From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NJ8z0-0002E9-AZ
	for qemu-devel@nongnu.org; Fri, 11 Dec 2009 12:08:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NJ8yv-0002C1-8M
	for qemu-devel@nongnu.org; Fri, 11 Dec 2009 12:08:45 -0500
Received: from [199.232.76.173] (port=46015 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NJ8yu-0002Bw-Qf
	for qemu-devel@nongnu.org; Fri, 11 Dec 2009 12:08:40 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]:47647)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16)
	(Exim 4.60) (envelope-from <daahern@cisco.com>) id 1NJ8yp-0005nV-OO
	for qemu-devel@nongnu.org; Fri, 11 Dec 2009 12:08:40 -0500
Message-ID: <4B227C7E.3090807@cisco.com>
Date: Fri, 11 Dec 2009 10:08:14 -0700
From: "David S. Ahern" <daahern@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Qemu terminating with SIGABRT
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, kvm-devel <kvm@vger.kernel.org>

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,
-- 
David Ahern