Segmentation fault on Linux

[Mikael Pettersson]

Edmund Dengler writes:
 > Howdy!
 > 
 > I did the run, but probably not what was expected. Is there a "compile so
 > the binary is debuggable" option for configuration?
 > 
 > # export ROOTDIR=/opt/pkgs/erlang/10b-7/lib/erlang
 > BINDIR=$ROOTDIR/erts-5.4.9/bin EMU=beam PROGNAME=erl
 > 
 > # gdb
 > GNU gdb 6.0
 > Copyright 2003 Free Software Foundation, Inc.
 > GDB is free software, covered by the GNU General Public License, and you are
 > welcome to change it and/or distribute copies of it under certain conditions.
 > Type "show copying" to see the conditions.
 > There is absolutely no warranty for GDB.  Type "show warranty" for details.
 > This GDB was configured as "i686-pc-linux-gnu".
 > (gdb) file lib/erlang/erts-5.4.9/bin/erlexec
 > Reading symbols from lib/erlang/erts-5.4.9/bin/erlexec...done.
 > Using host libthread_db library "/lib/libthread_db.so.1".
 > (gdb) r -- -root /opt/pkgs/erlang/10b-7/bin
 > Starting program: /opt/pkgs/erlang/10b-7/lib/erlang/erts-5.4.9/bin/erlexec
 > -- -root /opt/pkgs/erlang/10b-7/bin
 > warning: Unable to find dynamic linker breakpoint function.
 > GDB will be unable to debug shared library initializers
 > and track explicitly loaded dynamic code.
 > Detaching after fork from child process 835.
 > Detaching after fork from child process 839.
 > 
 > Program received signal SIGSEGV, Segmentation fault.
 > 0x401ac16e in ?? ()
 > (gdb) bt
 > #0  0x401ac16e in ?? ()
 > (gdb)
 > 
 > Regards!
 > Ed
 > 
 > On Fri, 23 Sep 2005, Bjorn Gustavsson wrote:
 > 
 > > Could you please run gdb on the core dump and print the stack backtrace
 > > so that we can see where it crashed?
 > >
 > > /Bjorn

1) file core.$pid
   to figure out which executable dumped it
2) gdb /path/to/otp/bin/$executable core.$pid