Caller for abort() is unknown in the backtrace, any suggestions to debug this

Question

I'm trying to debug one of my crashes and it seems to be caused by the abort raised from some where, and my gdb is not giving the caller details instead just shows few frames in the callstack. Any suggestions would be most welcome in debugging this issue.

(gdb) bt
#0  0x76453fc4 in raise () from /lib/libc.so.0
#1  0x7644d654 in abort () from /lib/libc.so.0
#2  0x7644cc4c in ?? () from /lib/libc.so.0
warning: GDB can't find the start of the function at 0x7644cc4a.

Answer 1

The truncated stack trace you get is most often caused by a mismatch between libc.so.6 that you used when looking at the core, and the one that was used to produce that core.

Given that you talk about buildroot, it seems likely that that might have happened.

You are debugging a core dump, and not a live process, right?

Answer 2

Use valgrind. It will be useful to compile with debug information (-g using GCC) before using valgrind.