From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] Signal trampoline unwinder for hppa-hpux
Date: Mon, 24 May 2004 17:38:00 -0000 [thread overview]
Message-ID: <40B23320.90201@gnu.org> (raw)
In-Reply-To: <20040523002931.GO7207@tausq.org>
The signal trampoline on hpux actually has a name (_sigreturn), so it
fails the check in tramp_frame_sniffer ()
is this more efficient/correct? It doesn't do any code reading just
checks the pc against "_sigreturn".
Yes, definitly. Having to do instruction examination should be
considered a last resource.
Andrew
next prev parent reply other threads:[~2004-05-24 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 4:17 Randolph Chung
2004-05-20 20:46 ` Joel Brobecker
2004-05-20 20:53 ` Randolph Chung
2004-05-20 22:36 ` Joel Brobecker
2004-05-20 23:33 ` Joel Brobecker
2004-05-21 17:41 ` Andrew Cagney
2004-05-21 18:39 ` Randolph Chung
2004-05-22 1:58 ` Randolph Chung
2004-05-23 0:29 ` Randolph Chung
2004-05-24 17:38 ` Andrew Cagney [this message]
2004-05-26 5:36 ` Randolph Chung
2004-05-26 13:20 ` Daniel Jacobowitz
2004-05-22 18:30 John David Anglin
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=40B23320.90201@gnu.org \
--to=cagney@gnu.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