From: Nick Clifton <nickc@cambridge.redhat.com>
To: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
Cc: ac131313@cygnus.com, binutils@sources.redhat.com,
gdb@sources.redhat.com, Chabane.Rezzik@usa.alcatel.com,
gnu-gdb-bug@gnu.org
Subject: Re: [Fwd: [Fwd: Caught signal 9 in core file ????]]
Date: Sat, 24 Nov 2001 10:06:00 -0000 [thread overview]
Message-ID: <m3bshlx3ym.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <200111192141.WAA14933@reisser.regent.e-technik.tu-muenchen.de>
Hi Peter,
> > I can see why you would want to preserve the signal, but shouldn't you
> > also preserve the PID (and any other core related data) as well ? In
> > fact isn't this really a multithreading problem, with a single BFD
> > structure being used to represent multiple (potential) thread cores ?
>
> It wouldn't matter for Solaris (and as I said, using the first note section
> for the signal in the currently running thread is a Solaris convention, which
> might not be true on other platforms), as prstat.pr_pid is the same for all
> threads.
> Using per thread signal/pid descriptions would gain nothing on Solaris, as
> the pid is all the same and the signal in all not currently running threads
> is SIGKILL. I suspect that something similar will happen on other platforms
> as well though.
Fair enough, in which case I will apply the patch. I realise that
this is not a full solution, but if it helps to get the ball rolling,
then that is a good thing.
Cheers
Nick
WARNING: multiple messages have this Message-ID
From: Nick Clifton <nickc@cambridge.redhat.com>
To: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
Cc: ac131313@cygnus.com, binutils@sources.redhat.com,
gdb@sources.redhat.com, Chabane.Rezzik@usa.alcatel.com,
gnu-gdb-bug@gnu.org
Subject: Re: [Fwd: [Fwd: Caught signal 9 in core file ????]]
Date: Thu, 29 Nov 2001 02:34:00 -0000 [thread overview]
Message-ID: <m3bshlx3ym.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
Message-ID: <20011129023400.gBOCNIgmoR_1vub-hPK2C5LoKvwmGE4n3RoAHp6Ydxc@z> (raw)
In-Reply-To: <200111192141.WAA14933@reisser.regent.e-technik.tu-muenchen.de>
Hi Peter,
> > I can see why you would want to preserve the signal, but shouldn't you
> > also preserve the PID (and any other core related data) as well ? In
> > fact isn't this really a multithreading problem, with a single BFD
> > structure being used to represent multiple (potential) thread cores ?
>
> It wouldn't matter for Solaris (and as I said, using the first note section
> for the signal in the currently running thread is a Solaris convention, which
> might not be true on other platforms), as prstat.pr_pid is the same for all
> threads.
> Using per thread signal/pid descriptions would gain nothing on Solaris, as
> the pid is all the same and the signal in all not currently running threads
> is SIGKILL. I suspect that something similar will happen on other platforms
> as well though.
Fair enough, in which case I will apply the patch. I realise that
this is not a full solution, but if it helps to get the ball rolling,
then that is a good thing.
Cheers
Nick
next prev parent reply other threads:[~2001-11-29 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3adxww98v.fsf@north-pole.nickc.cambridge.redhat.com>
2001-11-08 14:53 ` Peter.Schauer
2001-11-24 10:06 ` Nick Clifton [this message]
2001-11-29 2:34 ` Nick Clifton
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=m3bshlx3ym.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=Chabane.Rezzik@usa.alcatel.com \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--cc=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=gnu-gdb-bug@gnu.org \
/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