Re: gdb and libc debug symbols

[Martin Husemann <martin%duskware.de@localhost>]

On Sun, May 04, 2014 at 09:08:33PM +0200, Timo Buhrmester wrote:
> But still no additinal information the backtrace.
> | (gdb) bt full
> | #0  0x00007f7ff7439538 in read () from /usr/lib/libc.so.12
> | No symbol table info available.
> | [...]

Read is a system call, what you see is a crash in the (tiny) assembler
stub in libc. There is no C code for this, it is generated on the fly
straight in asm.

Try: x/16i read

This should show you were exactly it crashes. However, there are few
reasons to crash there, so something really bad (like stack smashing)
has happend, and most likely you are looking only at artefacts.

info reg

will give you more info about the cpu state at the point of the crash.


Martin