This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/rfa] allow unwinding "past main" for dummy frames
- From: Daniel Jacobowitz <drow at false dot org>
- To: Randolph Chung <randolph at tausq dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 5 Dec 2004 22:40:13 -0500
- Subject: Re: [patch/rfa] allow unwinding "past main" for dummy frames
- References: <20041206032726.GB6359@tausq.org>
On Sun, Dec 05, 2004 at 07:27:26PM -0800, Randolph Chung wrote:
> On hpux, we push a small bit of code on the stack to implement function
> calls from gdb. The stack trampoline contains a return address that
> points back to the current function. this is needed to properly restore
> the space registers (see hppa_hpux_push_dummy_code in hppa-hpux-tdep.c
> for a much more detailed explanation). The upshot of all of this is
> that when we do a backtrace from a gdb-called function, a backtrace can
> be prematurely truncated at a dummy frame. Since it doesn't make sense
> anyway to stop unwinding at dummy frames, this patch skips the "main
> function" detection logic for dummy frames. The same logic is already
> there for checking against the entry function a bit farther down in
> get_prev_frame ().
>
> ok?
Could you explain to me how inside_main_func is returning true for a
dummy frame?
The code is there for inside_entry_func because we used to use the
actual entry point as a location for the dummy frame.
--
Daniel Jacobowitz