[erlang-questions] beam process dies with code 135 (SIGBUS)
Tue Feb 17 14:34:03 CET 2009
On Tue, Feb 17, 2009 at 13:26, Mikael Pettersson <mikpe@REDACTED> wrote:
> Vlad Dumitrescu writes:
> > Does anyone have any experience of runtimes dying with code 135,
> > meaning by signal 7 (SIGBUS) (i.e. Bus error (bad memory access)) on
> > Linux?
> SIGBUS on x86 can AFAIK only be triggered by alignment errors,
> which for x86 user-mode code means largish data transfers using
> SSE instructions.
> Debugging this requires a core dump and the corresponding beam
> executable. If you're not getting core dumps, see if they've
> been disabled by default (man ulimit or limit).
Yes, the core dumps are disabled. I'll see what I can do about that.
More information about the erlang-questions