beam got SIGSEGV

Alexey Shchepin alexey@REDACTED
Fri Dec 19 10:57:18 CET 2003


Hi!

Hour ago ejabberd on jabber.ru get SIGSEGV:

This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
Core was generated by `beam'.
Program terminated with signal 11, Segmentation fault.
...
(gdb) bt
#0  0x80ba22e in erts_deep_process_dump ()
#1  0x80b9a23 in erts_deep_process_dump ()
#2  0x80b97fd in erts_deep_process_dump ()
#3  0x80b2069 in erl_crash_dump ()
#4  0x807164f in erl_exit ()
#5  0x80818f4 in make_hash2 ()
#6  0x80a55e0 in db_get_hash ()
#7  0x809a5ce in ets_lookup_2 ()
#8  0x80be03b in process_main ()
#9  0x8071573 in erl_start ()
#10 0x806319c in main ()
#11 0x80630ee in _start ()

Also erl_crash.dump was created, which starts with following lines:

=erl_crash_dump:0.1
Fri Dec 19 11:22:26 2003
Slogan: Invalid tag in make_hash2(0x0)
System version: Erlang (BEAM) emulator version 5.3 [source] [hipe]

I can send URLs to core dump and erl_crash.dump to one of Erlang
developers.

BEAM was started with "+Mea r10b" options.




More information about the erlang-bugs mailing list