From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MLgiS-0004At-UM
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 13:01:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MLgiR-0004A9-76
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 13:01:56 -0400
Received: from [199.232.76.173] (port=49614 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MLgiQ-00049y-TH
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 13:01:54 -0400
Received: from naru.obs2.net ([84.20.150.76]:37546)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <nchip@kos.to>) id 1MLgiQ-0008II-As
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 13:01:54 -0400
Date: Tue, 30 Jun 2009 20:01:45 +0300
From: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH 3/5] linux-user: do not avoid dumping of
	qemu itself
Message-ID: <20090630170145.GA7830@kos.to>
References: <cover.1246370192.git.riku.voipio@iki.fi>
	<14dcb210bb69620dd6a6912c66827da3aba4784c.1246370192.git.riku.voipio@iki.fi>
	<200906301552.12732.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200906301552.12732.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: qemu-devel@nongnu.org, arnaud.patard@rtp-net.org

On Tue, Jun 30, 2009 at 03:52:12PM +0100, Paul Brook wrote:
> On Tuesday 30 June 2009, riku.voipio@iki.fi wrote:
> > From: Riku Voipio <riku.voipio@iki.fi>
> >
> > Previously we disabled dumping of qemu itself if we already
> > created coredump of the target process. This broke the abort01
> > LTP test and any application that used WCOREDUMP to find out
> > the child process dumped core. Remove this feature.

> Isn't this going to overwrite the guest core dump we just wrote?

No, since we make the guest dump as qemu_binary_date-time_pid.core,
while host core will be core or whatever is /proc/sys/kernel/core_pattern.
However, if we replace our adhoc naming with reading core_pattern, we
would indeed get overwritten.

> It sounds like WCOREDUMP is one of those things that just isn't going to work.
> i.e. we have to just accept the limitation and xfail the test.

If this how people feel, I'll be glad to drop this patch.

Riku