Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 25 Feb 2001 06:03:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 25 Feb 2001 06:03:20 -0500 Received: from f00f.stub.clear.net.nz ([203.167.224.51]:63501 "HELO metastasis.f00f.org") by vger.kernel.org with SMTP id ; Sun, 25 Feb 2001 06:03:14 -0500 Date: Mon, 26 Feb 2001 00:03:09 +1300 From: Chris Wedgwood To: Andi Kleen Cc: linux-kernel@vger.kernel.org Subject: Re: Core dumps for threads Message-ID: <20010226000309.B12962@metastasis.f00f.org> In-Reply-To: <20010224134523.O26109@valinux.com> <20010225221505.A12595@metastasis.f00f.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ak@suse.de on Sun, Feb 25, 2001 at 11:28:14AM +0100 X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/