From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Mention signal fixes in NEWS
Date: Thu, 13 May 2004 18:33:00 -0000 [thread overview]
Message-ID: <40A3BF84.2070203@gnu.org> (raw)
In-Reply-To: <usme4swlb.fsf@gnu.org>
+Many generic problems with GDB's signal handling code have been fixed.
+These include: support for sigaltstack and sigaction;
I'd prefer that we spell out what this ``support for sigaltstack and
sigaction'' means, in user-level terms. That is, what exactly didn't
work before and now does, when sigaltstack and sigaction are involved?
... include: backtraces through non-contigious stacks (see
sigaltstack(2)); recognition of sa_sigaction signal trampolines (see
sigaction(2)); ...
+Note that kernel and architecture specific limitations may still
+restrict this functionality (ref PR gdb/1639).
How about being more explicit here? What configurations have this
new support, and which don't? Can we list at least the more popular
platforms in each category?
That gets complicated. Since some features only work on specific
patched kernels. However we can probably safely state that the features
do work on ``i386 GNU/Linux systems that include a 2.4 kernel''.
Andrew
next prev parent reply other threads:[~2004-05-13 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 19:07 Andrew Cagney
2004-05-12 20:56 ` Daniel Jacobowitz
2004-05-12 21:04 ` Andrew Cagney
2004-05-13 4:52 ` Eli Zaretskii
2004-05-13 18:33 ` Andrew Cagney [this message]
2004-05-14 12:38 ` Eli Zaretskii
2004-05-14 15:44 ` Andrew Cagney
2004-05-15 8:23 ` Eli Zaretskii
2004-05-17 19:17 ` 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=40A3BF84.2070203@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@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