From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: [hpux] Improve sigtramp frame identification
Date: Sat, 19 Nov 2005 16:06:00 -0000 [thread overview]
Message-ID: <437F1F25.6040104@tausq.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
the old code used to be hardcoded to look for a "_sigreturn" function,
but according to the ABI, the signal frame can be identified by a
specific bit in the unwind record. Use that instead.
committed
randolph
[-- Attachment #2: hpux-sig.diff --]
[-- Type: text/x-patch, Size: 1007 bytes --]
2005-11-19 Randolph Chung <tausq@debian.org>
* hppa-hpux-tdep.c (hppa_hpux_sigtramp_unwind_sniffer): Rely on the
unwind record to determine a signal frame, instead of hardcoding
a function name.
Index: hppa-hpux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/hppa-hpux-tdep.c,v
retrieving revision 1.43
diff -u -p -r1.43 hppa-hpux-tdep.c
--- hppa-hpux-tdep.c 29 Oct 2005 21:31:45 -0000 1.43
+++ hppa-hpux-tdep.c 19 Nov 2005 12:43:47 -0000
@@ -1246,12 +1274,12 @@ static const struct frame_unwind hppa_hp
static const struct frame_unwind *
hppa_hpux_sigtramp_unwind_sniffer (struct frame_info *next_frame)
{
+ struct unwind_table_entry *u;
CORE_ADDR pc = frame_pc_unwind (next_frame);
- char *name;
- find_pc_partial_function (pc, &name, NULL, NULL);
+ u = find_unwind_entry (pc);
- if (name && strcmp(name, "_sigreturn") == 0)
+ if (u && u->HP_UX_interrupt_marker)
return &hppa_hpux_sigtramp_frame_unwind;
return NULL;
next reply other threads:[~2005-11-19 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 16:06 Randolph Chung [this message]
2005-12-07 1:18 ` Mark Kettenis
2005-12-07 17:54 ` Randolph Chung
2005-12-13 10:00 ` Mark Kettenis
2005-12-13 10:06 ` Randolph Chung
2005-12-13 20:20 ` Mark Kettenis
2005-12-13 20:35 ` Randolph Chung
2005-12-07 19:31 ` Randolph Chung
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=437F1F25.6040104@tausq.org \
--to=randolph@tausq.org \
--cc=gdb-patches@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