What exactly is the purpose of logging all unhandled breakpoint instructions encountered <i>in user-mode code</i> to the syslog, and then continuing...? On Windows, a breakpoint instruction encountered outside of a debugger causes the standard error dialog to appear, and if you choose not to attach a debugger, the process terminates. IMHO that&#x27;s more reasonable behaviour, as breakpoint instructions shouldn&#x27;t appear in code that&#x27;s not being debugged (either by a debugger or itself, as is sometimes the case like the author does here.)<p><i>because unprivileged user-space code is able to force the kernel to waste a lot of time printing messages, slowing the whole system down</i><p>User code can do that already, or even just run in an infinite loop.