From: Mark Kettenis <kettenis@chello.nl>
To: drow@false.org
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: [mips] When to use a proc_desc
Date: Tue, 06 Apr 2004 23:34:00 -0000 [thread overview]
Message-ID: <200404062333.i36NXYtK001226@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040406215810.GA28116@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 6 Apr 2004 17:58:10 -0400)
Date: Tue, 6 Apr 2004 17:58:10 -0400
From: Daniel Jacobowitz <drow@false.org>
On Tue, Apr 06, 2004 at 05:56:46PM -0400, Andrew Cagney wrote:
> >I'll need to study this further, however, look at HP/UX.
> >
> >That unwinder checks its equivalent PDR against the prologue, ticking each
> >register off as it is encountered.
>
> I think the long answer is the same -- look at HP/UX. Fetch the PDR and
> then compare it against the instructions up-to $pc to see how many of
> those stores actually occured.
I think that defeats the point of having the proc_desc in the first
place. If we're only going to acknowledge register saves that we can
'easily' find, then why bother reading any of this out of the proc_desc
at all?
Because it allows one to determine where the prologue actually ends,
which is after all registers described by the descriptor have been
saved.
Mark
next prev parent reply other threads:[~2004-04-06 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:26 Daniel Jacobowitz
2004-03-25 16:22 ` Andrew Cagney
2004-04-06 21:56 ` Andrew Cagney
2004-04-06 21:58 ` Daniel Jacobowitz
2004-04-06 23:34 ` Mark Kettenis [this message]
2004-04-07 4:48 ` Daniel Jacobowitz
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=200404062333.i36NXYtK001226@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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