debugging VM segfaults

Adam Kocoloski <>
Sat Mar 13 01:38:21 CET 2010

Hi all, I can pretty reliably trigger a segfault in a distributed Erlang system I'm running.  I've seen it happen in both 13B01 and 13B04.  The backtrace generally looks like

#0  do_minor (p=0x7f2bbbc63560, new_sz=<value optimized out>, objv=0x1, nobj=1) at beam/erl_gc.c:909
#1  0x00000000004f7eb8 in erts_garbage_collect (p=0x7f2bbbc63560, need=0, objv=0x1, nobj=1) at beam/erl_gc.c:764
#2  0x00000000004f8b79 in erts_gc_after_bif_call (p=0x9, result=0, regs=0x215f330, arity=139824735676640) at beam/erl_gc.c:322
#3  0x0000000000551efd in .gc_after_bif () at hipe/hipe_amd64_glue.S:349
#4  0x00007f2b7bb3ba38 in ?? ()
#5  0x0000000000555e99 in nbif_unlink_1 () at x86_64-unknown-linux-gnu/opt/smp/hipe_amd64_bifs.S:6821

Happy to upload a full core dump somewhere if it would be helpful.  I'm not getting an erl_crash.dump.  Any thoughts on what the next step might be?  Best,


More information about the erlang-questions mailing list