[erlang-questions] Erlang initiated kernel panic on OSX
Thu Nov 29 14:56:00 CET 2012
It is a wrong guess.
Most people have never met this bug, because they use keyboard in Terminal
and close it with Ctrl+D after exiting Erlang with Ctrl+C
On Thu, Nov 29, 2012 at 5:44 PM, <acidbriggs@REDACTED> wrote:
> I have decided to just avoid the problem by using a windowed version of
> GNU Emacs instead of being a purist and using a terminal application. I am
> very new to Erlang (and I find it wonderful) and have finally become an
> emacs convert after all these wasted years using other tools. I wanted to
> really learn emacs without any help from a mouse so I opted for the
> terminal. If I can easily avoid this problem by using the windowed version
> of GNU emacs then so be it. I hope Apple will fix the bug in the kernel as
> this is just an open security/stability issue if it can be easily exploited
> (which it seems it can).
> Anyway, my guess is most people aren't coding in the terminal and that
> would reduce the risk of the panic.
> On Nov 28, 2012, at 7:01 PM, Scott Lystig Fritchie <fritchie@REDACTED>
> > acidbriggs@REDACTED wrote:
> > a> On Nov 27, 2012, at 11:56 AM, Loïc Hoguin <essen@REDACTED> wrote:
> >>> Is it doing it with kernel polling disabled?
> > a> Correct: Erlang R15B02 (erts-5.9.2) [source] [64-bit] [smp:4:4]
> > a> [async-threads:0] [hipe] [kernel-poll:false]
> > Howdy. It's been several months since I've seen this kernel panic, but
> > it has indeed happened to me while using Terminal.app and closing a
> > window while Riak was running inside. Riak typically uses +K true,
> > FWIW. Lion was the last time. I haven't been running Mountain Lion
> > long enough + an Erlang VM running in a Terminal.app window + closing
> > that window.
> > -Scott
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions