From: Daniel Jacobowitz <dan@debian.org>
To: Robert Love <rml@tech9.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PID of multi-threaded core's file name is wrong in 2.5.59
Date: Tue, 28 Jan 2003 12:49:53 -0500 [thread overview]
Message-ID: <20030128174953.GA23424@nevyn.them.org> (raw)
In-Reply-To: <1043775771.9069.63.camel@phantasy>
On Tue, Jan 28, 2003 at 12:42:52PM -0500, Robert Love wrote:
> On Tue, 2003-01-28 at 12:39, Daniel Jacobowitz wrote:
>
> > That wasn't my point. All of the other threads have already terminated
> > without dumping core at tis point; I don't think it's possible for two
> > threads of a CLONE_THREAD application to both dump core. See
> > fs/exec.c:coredump_wait.
> >
> > Also, once one thread gets into do_coredump it clears mm->dumpable;
> > nothing else will dump core from that MM anyway.
>
> Are you telling me only one thread per thread group can coredump,
> period? So if two of them segfault (say concurrently on two different
> processors) only one will win the race to dump and the others will
> simply exit?
That's right. The dump will include all the threads anyway, now.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-28 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 4:56 PID of multi-threaded core's file name is wrong in 2.5.59 MAEDA Naoaki
2003-01-28 12:21 ` Alan Cox
2003-01-28 15:45 ` Daniel Jacobowitz
2003-01-28 17:27 ` Robert Love
2003-01-28 17:39 ` Daniel Jacobowitz
2003-01-28 17:42 ` Robert Love
2003-01-28 17:49 ` Daniel Jacobowitz [this message]
2003-01-28 18:49 ` Alan Cox
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=20030128174953.GA23424@nevyn.them.org \
--to=dan@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maeda.naoaki@jp.fujitsu.com \
--cc=rml@tech9.net \
/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