From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MMMCS-0007VX-TG
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 09:19:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MMMCN-0007Su-QW
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 09:19:39 -0400
Received: from [199.232.76.173] (port=50573 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MMMCN-0007So-Jk
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 09:19:35 -0400
Received: from mx20.gnu.org ([199.232.41.8]:59057)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MMMCN-0006X5-Dx
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 09:19:35 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MMMCM-0007iJ-2G
	for qemu-devel@nongnu.org; Thu, 02 Jul 2009 09:19:34 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 3/5] linux-user: do not avoid dumping of qemu
	itself
Date: Thu, 2 Jul 2009 14:19:29 +0100
References: <cover.1246370192.git.riku.voipio@iki.fi>
	<200907020032.00212.paul@codesourcery.com>
	<20090702021921.GB18372@shareable.org>
In-Reply-To: <20090702021921.GB18372@shareable.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <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: Jamie Lokier <jamie@shareable.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org, Arnaud Patard <arnaud.patard@rtp-net.org>

> > [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).

Paul