From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Weil <weil@mail.berlios.de>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Sat, 12 Dec 2009 09:52:11 +0100
Message-ID: <4B2359BB.9070703@mail.berlios.de>
References: <4B227C7E.3090807@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
To: "David S. Ahern" <daahern@cisco.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from moutng.kundenserver.de ([212.227.126.187]:65125 "EHLO
	moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751628AbZLLIwP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sat, 12 Dec 2009 03:52:15 -0500
In-Reply-To: <4B227C7E.3090807@cisco.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.