From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: [mips] When to use a proc_desc
Date: Thu, 25 Mar 2004 16:22:00 -0000 [thread overview]
Message-ID: <4062FCC4.5080102@gnu.org> (raw)
In-Reply-To: <20040325040322.GA12885@nevyn.them.org>
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.
Andrew
next prev parent reply other threads:[~2004-03-25 15:37 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 [this message]
2004-04-06 21:56 ` Andrew Cagney
2004-04-06 21:58 ` Daniel Jacobowitz
2004-04-06 23:34 ` Mark Kettenis
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=4062FCC4.5080102@gnu.org \
--to=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