This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Interpreting a gdb backtrace


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.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]