From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MMYON-0003bw-QO
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 22:20:47 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MMYOJ-0003bJ-HE
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 22:20:47 -0400
Received: from [199.232.76.173] (port=58416 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MMYOJ-0003bG-Cn
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 22:20:43 -0400
Received: from mail2.shareable.org ([80.68.89.115]:55993)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1MMYOJ-0005mV-0n
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 22:20:43 -0400
Date: Fri, 3 Jul 2009 03:20:35 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [PATCH 3/5] linux-user: do not avoid dumping of qemu
	itself
Message-ID: <20090703022035.GB938@shareable.org>
References: <cover.1246370192.git.riku.voipio@iki.fi>
	<200907020032.00212.paul@codesourcery.com>
	<20090702021921.GB18372@shareable.org>
	<200907021419.30327.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200907021419.30327.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org, Arnaud Patard <arnaud.patard@rtp-net.org>

Paul Brook wrote:
> > > [1] A host core dump may be useful for debugging qemu itself, but that's
> > > a fairly specialized corner case, and not necessarily something we want
> > > to be exposing to users.
> >
> > It would make sense to set RLIMIT_CORE to zero very early in
> > qemu-user, and then someone debugging qemu-user can easily change
> > RLIMIT_CORE from gdb while it is running.
> 
> Sounds reasonable, as long as you're careful to avoid breaking guest 
> applications that call {get,set}rlimit(RLIMIT_CORE).

They should not be sent to the host, but affect guest core dumping
instead.  (Um, probably).

-- Jamie