[erlang-questions] beam process dies with code 135 (SIGBUS)
Tue Feb 17 11:13:33 CET 2009
Does anyone have any experience of runtimes dying with code 135,
meaning by signal 7 (SIGBUS) (i.e. Bus error (bad memory access)) on
We have seen nodes going down with this reason relatively often (but
randomly) and I don't know how to locate the problem. There doesn't
seem to be any code dump.
Could this be triggered by something internal?
This is a SUSE distribution with
> uname -a
Linux selnx120 126.96.36.199-0.16-bigsmp #1 SMP Tue Oct 2 16:57:49 UTC
2007 i686 i686 i386 GNU/Linux
More information about the erlang-questions