Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: dwarf2 and frame bases
Date: Thu, 11 Nov 2004 23:33:00 -0000	[thread overview]
Message-ID: <20041111233249.GA2305@nevyn.them.org> (raw)
In-Reply-To: <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


      reply	other threads:[~2004-11-11 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041110235149.GO15714@tausq.org>
     [not found] ` <20041110235649.GA741@nevyn.them.org>
     [not found]   ` <20041111000933.GP15714@tausq.org>
     [not found]     ` <20041111030938.GA4784@nevyn.them.org>
     [not found]       ` <20041111164852.GS15714@tausq.org>
     [not found]         ` <20041111171232.GA10326@nevyn.them.org>
2004-11-11 21:18           ` Randolph Chung
2004-11-11 23:33             ` Daniel Jacobowitz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041111233249.GA2305@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox