From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LmPc0-0007kY-5g
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 05:41:28 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LmPbu-0007j2-OA
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 05:41:27 -0400
Received: from [199.232.76.173] (port=59479 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LmPbu-0007it-86
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 05:41:22 -0400
Received: from mx2.redhat.com ([66.187.237.31]:58718)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1LmPbt-0005kE-QZ
	for qemu-devel@nongnu.org; Wed, 25 Mar 2009 05:41:22 -0400
Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26])
	by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n2P9fJ9E008586
	for <qemu-devel@nongnu.org>; Wed, 25 Mar 2009 05:41:19 -0400
Message-ID: <49C9FC3D.6010704@redhat.com>
Date: Wed, 25 Mar 2009 11:41:17 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Kernel core dumps from qemu
References: <20090324165401.GA2999@ldl.fc.hp.com> <49C921A6.3070202@redhat.com>
	<20090324201924.GA27406@ldl.fc.hp.com>
In-Reply-To: <20090324201924.GA27406@ldl.fc.hp.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
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: qemu-devel@nongnu.org
Cc: anderson@redhat.com

Chris Smith wrote:
> On Tue, Mar 24, 2009 at 08:08:38PM +0200, Avi Kivity wrote:
>
>   
>> I'd suggest a 'format' argument, so we can extend this later to dump
>> in non-ELF formats (the Windows native memory dump format would be
>> useful).
>>     
>
> No problem.  I was thinking of something similar --
>
>     (qemu) dump | winfmt > win.dmp
>
> or
>
>     (qemu) dump | /usr/bin/gdbfmt > just.like.vmcore
>
> or
>
>     (qemu) dump > raw.elf		[normal case for crash utility]
>
> with qemu providing a dump primitive (just the data) to be dressed up
> by tools distributed with qemu, or contributed, or home grown.
>
> The | and > are just to be explicit, it could be prettier.
>
>   

I suggest 'dump -filter ... blah'. I guess for larger cores this is 
better than postprocessing, if it can be done without buffering all of RAM.

-- 
error compiling committee.c: too many arguments to function