From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Deprecate SIGTRAMP_START SIGTRAMP_END
Date: Tue, 23 Mar 2004 15:18:00 -0000 [thread overview]
Message-ID: <40605533.6070003@gnu.org> (raw)
In-Reply-To: <40576B65.9020700@gnu.org>
> Hello,
>
> The attached deprecates SIGTRAMP_START and SIGTRAMP_END. These were made obsolete by PC_IN_SIGTRAMP (which in turn has been made obsolete by signal trampoline frame sniffers).
>
> Note that blockframe.c:find_pc_partial_function contains what I consider to be broken references to these macros -- typically it is only possible to determine the location of a signal trampoline by doing a detailed analysis of the inferior (i.e., unwinding frames and examining instructions) yet that function is ment to work with just static information. I've added a comment explaining this.
>
> comments?
>
> I'll look to commit this in a week.
I've checked this in.
Andrew
> 2004-03-16 Andrew Cagney <cagney@redhat.com>
>
> * gdbarch.sh (SIGTRAMP_START, SIGTRAMP_END): Deprecate.
> * gdbarch.h, gdbarch.c: Re-generate.
> * i386obsd-tdep.c (i386obsd_init_abi): Update.
> * i386nbsd-tdep.c (i386nbsd_init_abi): Update.
> * i386bsd-tdep.c (i386bsd_init_abi): Update.
> * config/vax/tm-vaxbsd.h (DEPRECATED_SIGTRAMP_END)
> (DEPRECATED_SIGTRAMP_START): Update.
> * config/m68k/tm-nbsd.h (DEPRECATED_SIGTRAMP_END)
> (DEPRECATED_SIGTRAMP_START): Update.
> * blockframe.c (find_pc_sect_partial_function): Update.
> * arch-utils.c (legacy_pc_in_sigtramp): Update.
>
prev parent reply other threads:[~2004-03-23 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 21:02 Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-23 15:18 ` Andrew Cagney [this message]
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=40605533.6070003@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