<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Don't get me wrong, I have no doubts that it's an OS X bug. But, getting that fixed via Apple is next to impossible. I am not sure of the mechanism as to why it crashes the OS, but it does. It is reproducible. I was just hoping someone might know how to patch Erlang to help avoid the OS X bug as it's really irritating.</div><div><br></div><div>If anyone is curious you can see that the process that caused the panic was named "beam.smp":</div><div><br></div><div><div>Interval Since Last Panic Report: 2399141 sec</div><div>Panics Since Last Report: 1</div><div>Anonymous UUID: 1C24E5B9-05B7-8082-2863-4E5C3ECA6AEC</div><div><br></div><div>Thu Nov 15 11:44:13 2012</div><div>panic(cpu 2 caller 0xffffff8006d1fdca): "negative open count (c, 16, 3)"@/SourceCache/xnu/xnu-2050.18.24/bsd/miscfs/specfs/spec_vnops.c:1813</div><div>Backtrace (CPU 2), Frame : Return Address</div><div>0xffffff80f7e1bbe0 : 0xffffff8006c1d626 </div><div>0xffffff80f7e1bc50 : 0xffffff8006d1fdca </div><div>0xffffff80f7e1bc90 : 0xffffff8006d24c56 </div><div>0xffffff80f7e1bce0 : 0xffffff8006d11c96 </div><div>0xffffff80f7e1bd20 : 0xffffff8006d094af </div><div>0xffffff80f7e1bd50 : 0xffffff8006d08645 </div><div>0xffffff80f7e1bda0 : 0xffffff8006f4c56c </div><div>0xffffff80f7e1be10 : 0xffffff8006f4cae6 </div><div>0xffffff80f7e1be50 : 0xffffff8006f5697b </div><div>0xffffff80f7e1bec0 : 0xffffff8006c39cc9 </div><div>0xffffff80f7e1bef0 : 0xffffff8006c3c7c8 </div><div>0xffffff80f7e1bf20 : 0xffffff8006c3c63e </div><div>0xffffff80f7e1bf50 : 0xffffff8006c1b70d </div><div>0xffffff80f7e1bf90 : 0xffffff8006cb8163 </div><div>0xffffff80f7e1bfb0 : 0xffffff8006cce4bc </div><div><br></div><div>BSD process name corresponding to current thread: beam.smp</div><div><br></div><div>Mac OS version:</div><div>12C60</div></div><div><br></div><div><br></div><div><br></div><div>On Nov 26, 2012, at 3:51 PM, Max Lapshin <<a href="mailto:max.lapshin@gmail.com">max.lapshin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">How erlang be guilty in killing kernel of unix OS? It isn't DOS<br>What is the exact mechanism of this Mac failure (and it is definitely Mac failure, not erlang failure).<br><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Nov 27, 2012 at 12:28 AM, <span dir="ltr"><<a href="mailto:acidbriggs@gmail.com" target="_blank">acidbriggs@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
Back in March of 2010 it was reported that it was possible to initiate a kernel panic on OS X 10.6.2 with Erlang.<br>
<br>
Does anyone know if there is a fix for this? This is still happening in OS X 10.8.2 with Erlang R15B02. I've had it happen on all three of my Macs when working in Emacs and killing an Erlang shell in a buffer in a non-clean way.<br>
<br>
I know that the problem was reported to Apple but we know how that is.<br>
<br>
Perhaps someone has some sort of patch that can be applied to Erlang that can stop it from exploiting this flaw?<br>
<br>
Thanks for your time,<br>
<br>
<br>
Briggs<br>
<br>
<br>
<br>
<br>
The original thread (<a href="http://erlang.org/pipermail/erlang-questions/2010-March/050112.html" target="_blank">http://erlang.org/pipermail/erlang-questions/2010-March/050112.html</a>) stated:<br>
<br>
<br>
Greetings,<br>
<br>
Using Snow Leopard 10.6.2 and Erlang R13B04 it's possible to cause a<br>
kernel panic using the following steps:<br>
<br>
1. Start new terminal window<br>
2. erl +K true -s crypto<br>
3. Cmd-W (close the terminal window without stopping erlang)<br>
<br>
Alternatively, if you're running SL 10.6.2 and Erlang R13B03:<br>
<br>
1. Start new terminal window<br>
2. erl +K true -s crypto<br>
3. Cmd-Q (quit the terminal app without stopping erlang)<br>
<br>
This appears to work with either 32 or 64 bit builds of Erlang.<br>
<br>
<br>
Thanks,<br>
<br>
D.<br>
<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>