Re: [RFC/hppa] Change handling of stubs in the return path

[Randolph Chung <randolph at tausq dot org>]

> When you step one instruction out of the function, you go from "frame
> A, called by frame B" to "frame C, called by frame B".  Does GDB get
> confused by this?  Try using "step"; it may decide that frame C was
> called by frame A, and resume.
> 
> I guess that doesn't matter.  What usually happens in this case is GDB
> loses control; but if it does, it will just hit the dummy frame
> breakpoint, so who cares?

are you talking about the function called by gdb case [1]? or the normal
function-called-shared-library-function case [2]?

but it doesn't matter, it works :) although in the case of [1], when
stepping out of A, you will step through C (this is arguably a bug,
because gdb doesn't consider __gcc_plt_stub a solib return trampoline)

in the case of [2], we step out of A, into C, gdb automatically skips C
because it is a solib return trampoline, so we end up directly back in B
without stopping in C.

> I meant the missing space after _stub.

ah, ok. fixed.

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