From: Chris Wedgwood <cw@f00f.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Core dumps for threads
Date: Mon, 26 Feb 2001 00:03:09 +1300 [thread overview]
Message-ID: <20010226000309.B12962@metastasis.f00f.org> (raw)
In-Reply-To: <20010224134523.O26109@valinux.com> <E14WmhG-0000Yj-00@the-village.bc.nu> <20010225221505.A12595@metastasis.f00f.org> <oupk86fjbup.fsf@pigdrop.muc.suse.de>
In-Reply-To: <oupk86fjbup.fsf@pigdrop.muc.suse.de>; from ak@suse.de on Sun, Feb 25, 2001 at 11:28:14AM +0100
On Sun, Feb 25, 2001 at 11:28:14AM +0100, Andi Kleen wrote:
It would need a recursive mm semaphore -- core dumps can page
fault and page faults take the semaphore again. Other alternative
is to copy the MM like fork before dumping, but then core dumping
could fail much quicker when you ran out of memory.
Ouch... would creating another semaphore or flag 'dumping_core' work
or is that jut a bad idea?
I ask this because like it or not; people use threaded applications
and having threaded core dumps would be cool. Requiring a copy to
dump isn't really elegant or an option if you run a process who's RSS
is 400M on a 512MB machine as I do.
--cw
next prev parent reply other threads:[~2001-02-25 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 21:45 Core dumps for threads Don Dugger
2001-02-24 21:57 ` Alan Cox
2001-02-25 9:15 ` Chris Wedgwood
2001-02-25 9:40 ` Adam Fritzler
2001-02-26 0:36 ` davids
2001-02-25 10:28 ` Andi Kleen
2001-02-25 11:03 ` Chris Wedgwood [this message]
2001-02-25 13:57 ` Alan Cox
2001-02-27 17:29 ` [PATCH] " Don Dugger
2001-02-27 17:55 ` Alan Cox
2001-02-27 17:57 ` 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=20010226000309.B12962@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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 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.