Sunday, May 31, 2009

Creating and analysing coredump messages

1) Creating a core dump

a) Run the command ulimit -c unlimited

b) Run the executable that is crashing

c) You should see a message like "Segmentation fault (core dumped)"

2) Analysing core dump using gdb

a) Run the command

gdb

b) You should see the point of the crash (in the back trace)

Reading symbols from /lib/libcrypto.so.0.9.8...done.Loaded symbols for /lib/libcrypto.so.0.9.8Reading symbols from /lib/libresolv.so.2...done.Loaded symbols for /lib/libresolv.so.2Reading symbols from /lib/libc.so.6...done.Loaded symbols for /lib/libc.so.6Reading symbols from /lib/libdl.so.2...done.Loaded symbols for /lib/libdl.so.2Reading symbols from /lib/ld.so.1...done.Loaded symbols for /lib/ld.so.1

#0 0x0fd60954 in strlen () from /lib/libc.so.6

This means it is some problem with strlen .

No comments:

Post a Comment