From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [obish] Delete ppcnbsd_pc_in_sigtramp
Date: Fri, 30 Apr 2004 22:39:00 -0000 [thread overview]
Message-ID: <4092D5AE.2030603@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
Follow-up to adding a proper sigtramp unwinder to ppcnbsd - the old
pc_in_sigtramp code is no longer needed - removed.
committed,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1269 bytes --]
2004-04-30 Andrew Cagney <cagney@redhat.com>
* mipsnbsd-tdep.c (mipsnbsd_pc_in_sigtramp): Delete function.
(mipsnbsd_init_abi): Do not set pc_in_sigtramp.
Index: mipsnbsd-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mipsnbsd-tdep.c,v
retrieving revision 1.12
diff -p -u -r1.12 mipsnbsd-tdep.c
--- mipsnbsd-tdep.c 29 Apr 2004 18:28:43 -0000 1.12
+++ mipsnbsd-tdep.c 30 Apr 2004 22:36:50 -0000
@@ -221,13 +221,6 @@ mipsnbsd_sigtramp_offset (CORE_ADDR pc)
return -1;
}
-static int
-mipsnbsd_pc_in_sigtramp (CORE_ADDR pc, char *func_name)
-{
- return (nbsd_pc_in_sigtramp (pc, func_name)
- || mipsnbsd_sigtramp_offset (pc) >= 0);
-}
-
/* Figure out where the longjmp will land. We expect that we have
just entered longjmp and haven't yet setup the stack frame, so
the args are still in the argument regs. A0_REGNUM points at the
@@ -345,8 +338,6 @@ static void
mipsnbsd_init_abi (struct gdbarch_info info,
struct gdbarch *gdbarch)
{
- set_gdbarch_deprecated_pc_in_sigtramp (gdbarch, mipsnbsd_pc_in_sigtramp);
-
set_gdbarch_get_longjmp_target (gdbarch, mipsnbsd_get_longjmp_target);
set_gdbarch_cannot_fetch_register (gdbarch, mipsnbsd_cannot_fetch_register);
next reply other threads:[~2004-04-30 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 22:39 Andrew Cagney [this message]
2004-05-01 0:10 ` Andrew Cagney
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=4092D5AE.2030603@gnu.org \
--to=cagney@gnu.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