This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB 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]

Re: gdb stack trace problems (Addendum)


Christopher Faylor wrote:


If a function doesn't set up a frame pointer and there is no debugging information available, how would one derive a stack frame? I could imagine a really complicated "search the stack" technique but I can't see how it would ever be foolproof.

That's where GDB hacking just starts to get interesting. :-) Yes,
it's complicated and potentially expensive too, because you may have
to transfer a lot of bytes. The mips has something similar for
function starts, and a "heuristic-fence-post" variable to control
how hard to work at it.

Stan


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