Interpreting a gdb backtrace

[jojelino]

On 2012-05-19 AM 6:08, Ken Brown wrote:
> 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.
>
i think you should provide symbol file of emacs to gdb. if it was 
stripped, you had better to build emacs from source code with -g (at 
least gcc 4.5 for CFI that gdb need to backtrace the stack frame with ease).

-- 
Regards.




--
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