Hi,

I would like to analyze core dump after Linux user space application crash. In gdb I loaded symbols of executable application via "file" comand and then used "core" command to load and examine core dump file but received output on gdb which does not say a lot:

(gdb) core /home/igal/Android25_2/dbg/core
Error while mapping shared library sections:
/system/bin/linker: No such file or directory.
Error while mapping shared library sections:
libc.so: No such file or directory.
Error while mapping shared library sections:
libstdc++.so: No such file or directory.
Error while mapping shared library sections:
libm.so: No such file or directory.
Symbol file not found for /system/bin/linker
Symbol file not found for libc.so
Symbol file not found for libstdc++.so
Symbol file not found for libm.so
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Core was generated by `navilink'.
Program terminated with signal 11, Segmentation fault.
#0 0xafe18b88 in ?? ()

Could you advice?

Igal

Where was the application running when it crashed? That's the environment that will have the info gdb needs to help you.

Things I can think of:

Did you run a "ldd yourprogram" to find out how/where the libraries are being loaded from?

Did you link with stuff such as "-Wl,-rpath,/path/to/libraryset1 -Wl,-rpath,/path/to/libbraryset2" etc? (Alternatively, use $LD_LIBRARY_PATH for debugging purposes.)

For debugging it's useful to install the libraries' debugging symbols, typically they come in a separate package. E.g., glibc can have a separate glibc-dbg package for its symbols.

Hi does anyone have a good tutorial on the usage of GDB wherein I can quickly pickup the tool and its usage.

Ajit

http://www.gnu.org/software/gdb/documentation/

There's some tutorials in GDB's documentation.

GDB Tutorials

gdb for pthread debug

gdb core dump analysis for beginners

gdb tutorial how to start with GDB

zariga