<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>userbinator</author><text>What exactly is the purpose of logging all unhandled breakpoint instructions encountered &lt;i&gt;in user-mode code&lt;/i&gt; 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&amp;#x27;s more reasonable behaviour, as breakpoint instructions shouldn&amp;#x27;t appear in code that&amp;#x27;s not being debugged (either by a debugger or itself, as is sometimes the case like the author does here.)&lt;p&gt;&lt;i&gt;because unprivileged user-space code is able to force the kernel to waste a lot of time printing messages, slowing the whole system down&lt;/i&gt;&lt;p&gt;User code can do that already, or even just run in an infinite loop.</text><parent_chain></parent_chain></comment><story><title>The mystery of the fifteen-millisecond breakpoint instruction</title><url>http://blog.jwhitham.org/2015/04/the-mystery-of-fifteen-millisecond.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>caf</author><text>I&amp;#x27;m surprised the author didn&amp;#x27;t submit this patch back to the Linux ARM architecture maintainers - it seems entirely apropos.</text><parent_chain></parent_chain></comment><story><title>The mystery of the fifteen-millisecond breakpoint instruction</title><url>http://blog.jwhitham.org/2015/04/the-mystery-of-fifteen-millisecond.html</url></story>