Erlang Mailing Lists

Author Message

<  Erlang bugs mailing list  ~  beam got SIGSEGV

alexey at sevcom.net
Posted: Fri Dec 19, 2003 9:57 am Reply with quote
Guest
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.



Post generated using Mail2Forum (http://m2f.sourceforge.net)
alexey at sevcom.net
Posted: Mon Dec 22, 2003 11:16 am Reply with quote
Guest
Hi!

AS> Hi! Hour ago ejabberd on jabber.ru get SIGSEGV:

[...]

AS> BEAM was started with "+Mea r10b" options.

FYI: this bug is reproducible without this option. Now I have few
erl_crash.dump files, which ends with something like this:

=proc_heap:<0.8173.0>
C675BF8:lHFFFFFFFF|HC2B0178

After dumping of this line, erlang process got SIGSEGV. All core
dumps have same backtrace as in my previous message.


Post generated using Mail2Forum (http://m2f.sourceforge.net)
alexey at sevcom.net
Posted: Mon Dec 22, 2003 11:23 am Reply with quote
Guest
Hi!

AS> Hi! Hour ago ejabberd on jabber.ru get SIGSEGV:

[...]

AS> BEAM was started with "+Mea r10b" options.

FYI: this bug is reproducible without this option. Now I have few
erl_crash.dump files, which ends with something like this:

=proc_heap:<0.8173.0>
C675BF8:lHFFFFFFFF|HC2B0178

After dumping of this line, erlang process got SIGSEGV. All core
dumps have same backtrace as in my previous message.


Post generated using Mail2Forum (http://m2f.sourceforge.net)

Display posts from previous:  

All times are GMT
Page 1 of 1
This forum is locked: you cannot post, reply to, or edit topics.

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum