From: Andrew Morton <akpm@digeo.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, msinz@wgate.com
Subject: Re: [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl
Date: Fri, 20 Sep 2002 16:27:24 -0700 [thread overview]
Message-ID: <3D8BAEDC.ED943632@digeo.com> (raw)
In-Reply-To: p73bs6stfv8.fsf@oldwotan.suse.de
Andi Kleen wrote:
>
> Andrew Morton <akpm@digeo.com> writes:
>
> > True, but it's all more code and I don't believe that it adds
> > much value. It means that people need to run off and find
>
> One useful feature of it would be that you can get core dumps for
> each thread by including the pid (or tid later with newer threading libraries)
> Currently threads when core dumping overwrite each others cores so you lose
> the registers of all but one.
Oh sure, I agree that it's a useful feature. But I don't agree that
we need to allow users to specify how the final filename is pasted
together. Just give them host-uid-gid-comm.core. ie: everything.
next prev parent reply other threads:[~2002-09-20 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D8B87C7.7040106@wgate.com.suse.lists.linux.kernel>
[not found] ` <3D8B8CAB.103C6CB8@digeo.com.suse.lists.linux.kernel>
[not found] ` <3D8B934A.1060900@wgate.com.suse.lists.linux.kernel>
[not found] ` <3D8B982A.2ABAA64C@digeo.com.suse.lists.linux.kernel>
2002-09-20 23:12 ` [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl Andi Kleen
2002-09-20 23:27 ` Andrew Morton [this message]
2002-09-20 23:47 ` Andi Kleen
2002-09-21 20:19 ` Francois Romieu
2002-09-20 20:40 Michael Sinz
2002-09-20 20:59 ` Andrew Morton
2002-09-20 21:01 ` Andrew Morton
2002-09-20 21:29 ` Michael Sinz
2002-09-20 21:50 ` Andrew Morton
2002-09-20 21:53 ` Andrew Morton
2002-09-20 23:32 ` Michael Sinz
2002-09-22 19:02 ` Bill Davidsen
2002-09-22 23:59 ` Andrew Morton
2002-09-23 19:00 ` Michael Sinz
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=3D8BAEDC.ED943632@digeo.com \
--to=akpm@digeo.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=msinz@wgate.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.