From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Mon, 14 Dec 2009 14:04:05 -0200
Message-ID: <20091214140405.493ecbba@doriath>
References: <4B227C7E.3090807@cisco.com>
	<4B2359BB.9070703@mail.berlios.de>
	<4B23DC62.5090301@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Stefan Weil <weil@mail.berlios.de>, qemu-devel@nongnu.org,
	kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
To: "David S. Ahern" <daahern@cisco.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:21909 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1757586AbZLNQER (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 14 Dec 2009 11:04:17 -0500
In-Reply-To: <4B23DC62.5090301@cisco.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Sat, 12 Dec 2009 11:09:38 -0700
"David S. Ahern" <daahern@cisco.com> wrote:

> 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.

 Are you using qemu-kvm or upstream qemu? Which version? Don't you
have any procedure which would make the bug more likely to happen?

 Thanks.