From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NJWQd-0007P8-V4
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 13:10:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NJWQY-0007OM-KS
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 13:10:50 -0500
Received: from [199.232.76.173] (port=38347 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NJWQY-0007OJ-Bv
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 13:10:46 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]:44326)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16)
	(Exim 4.60) (envelope-from <daahern@cisco.com>) id 1NJWQY-0005AK-34
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 13:10:46 -0500
Message-ID: <4B23DC62.5090301@cisco.com>
Date: Sat, 12 Dec 2009 11:09:38 -0700
From: "David S. Ahern" <daahern@cisco.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
References: <4B227C7E.3090807@cisco.com> <4B2359BB.9070703@mail.berlios.de>
In-Reply-To: <4B2359BB.9070703@mail.berlios.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>

Thanks for the responses. I had forgotten that SIGABRT==abort() which
means I have to get the core file to get to the root cause. To date the
only information I have is a shell exit status of 134 which from the
bash man pages means it died due to SIGABRT.

David Ahern


On 12/12/2009 01:52 AM, Stefan Weil wrote:
> David S. Ahern schrieb:
>> I realize this is a rather generic question, but what are typical
>> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
>> somewhat regular (though not repeatable on demand) basis. I do not have
>> a core file, though I hope to capture one if I can get it repeat again.
>>
>> Thanks,
>>   
> 
> Look for "abort" in QEMU's code to see the possible reasons.
> 
> In many cases, the reason will be printed to stderr before
> aborting. Did you call QEMU from a console and get some
> output there? Or maybe the stderr output went into a file?
> 
> Run "ulimit -c unlimited" before you run QEMU, then a
> core file will be written automatically on SIGABRT.
>