This is the mail archive of the
mailing list for the Cygwin project.
Re: Interpreting a gdb backtrace
On 2012-05-19 AM 9:30, Ken Brown wrote:
Then, i suspect that some function is called with function pointer type
with different calling convention from itself, eventually stack frame is
broken and return address goes into wrong place.
I built emacs with -g -O0. gdb had the symbol table at the start of the
debugging session. It's just after the crash that everything is messed up.
if it is the case, there is nothing we can expect from gdb backtrace.
but at least we can inspect esp register ?? for example, type following
x $esp-c ...
x $esp-0x40(or greater than) and just enter until you get value which
seems to be return address.
and you can know what the return address is supposed to be(if it isn't
relocated but it is scarce.)
i hope you can find return address. then you can breakpoint the annoying
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple