Interpreting a gdb backtrace

Ken Brown
Fri May 18 21:09:00 GMT 2012

I'm trying to debug an emacs crash and am having trouble getting a 
useful backtrace after the crash.  Here's an example:

#0  0x00289c08 in ?? ()
No symbol table info available.
#1  0x007ba148 in _malloc_mutex ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Aside from the lack of information, the most salient feature of this is 
that _malloc_mutex is actually a variable, not a function, so the 
information for frame #1 makes no sense.

I'm not very experienced at debugging, but I'm wondering if I can get 
anything out of this sort of backtrace.  Or does it just indicate that 
the stack got corrupted?

Thanks in advance for any suggestions.


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list