Re: [RFC] Infinite backtraces...

[Randolph Chung <randolph@tausq.org>]

> I'll give it a try and see if we can skip them. I like the idea of
> having a switch to hide them, though. That would be very nice. but
> then we need to add a new type of frames. As far as I can tell
> (understand: from code inspection), the stub frames are marked as
> NORMAL_FRAMEs.
> 
> > see:
> > http://sources.redhat.com/ml/gdb-patches/2004-05/msg00741.html
> 
> Thanks muchly for the pointer. I missed that thread.

i just found another instance where these stub frames is causing
problems, and this one is not just "cosmetic" ...

suppose you are calling a function through a stub, so your stack frames
are:

#0 callee
#1 callee stub
#2 caller

if you do a "finish" from callee, gdb will stop in the callee stub
instead of at the caller. quite annoying :(

i'm wondering if we should make the hppa unwinders more export-stub
aware -- e.g. in hppa_frame_cache (), after we've determined the address
of the current frame, we can see if this is an "export stub" frame, and
if so automatically rewind one more frame. i think this should work and
shouldn't cause any problems.... thoughts?

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/