This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: dwarf2 and frame bases
- 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: Thu, 11 Nov 2004 18:32:49 -0500
- Subject: Re: dwarf2 and frame bases
- References: <20041110235149.GO15714@tausq.org> <20041110235649.GA741@nevyn.them.org> <20041111000933.GP15714@tausq.org> <20041111030938.GA4784@nevyn.them.org> <20041111164852.GS15714@tausq.org> <20041111171232.GA10326@nevyn.them.org> <20041111211740.GW15714@tausq.org>
On Thu, Nov 11, 2004 at 01:17:40PM -0800, Randolph Chung wrote:
> > Suppose we're in frame A, called from frame B. We're at the first
> > instruction. If we ask the sentinel frame to unwind the value of r3,
> > we'll get its real register value - regardless of where we are in the
> > sequence. If we ask frame A to unwind r3, we want to get frame B's r3.
> > Where frame A is in its prologue has no effect on what frame B's r3 was
> > at the time of calling A.
>
> ok ok, how about this fix? all the recurse.exp tests pass now.
>
> thanks,
> randolph
>
> 2004-11-11 Randolph Chung <tausq@debian.org>
>
> * hppa-tdep.c (hppa_frame_cache): Properly handle the frame pointer
> register so that it can be unwound from anywhere in the prologue.
Bingo! This patch is OK.
--
Daniel Jacobowitz