From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: [Fwd: Caught signal 9 in core file ????]
Date: Thu, 27 Sep 2001 11:49:00 -0000 [thread overview]
Message-ID: <20010927144929.A27697@nevyn.them.org> (raw)
In-Reply-To: <3BB37312.3000706@cygnus.com>
On Thu, Sep 27, 2001 at 02:42:26PM -0400, Andrew Cagney wrote:
> Anyone want to play with this? While a BFD bug, gdb is probably BFD's
> only core file customer.
Peter's patch looks right to me, though it's a little more complicated
after my recent BFD core changes - that test will need to be applied in
multiple places, I think.
I'm also not convinced that we can do this reliably; is the thread
which crashed always listed first in a dump? Or should we check that
pr_cursig is not SIGKILL instead?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-09-27 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 11:42 Andrew Cagney
2001-09-27 11:49 ` Daniel Jacobowitz [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=20010927144929.A27697@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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