From: Avi Kivity Subject: Re: Qemu terminating with SIGABRT Date: Sat, 12 Dec 2009 10:09:54 +0200 Message-ID: <4B234FD2.8080608@redhat.com> References: <4B227C7E.3090807@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm-devel To: "David S. Ahern" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49389 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753744AbZLLIJx (ORCPT ); Sat, 12 Dec 2009 03:09:53 -0500 In-Reply-To: <4B227C7E.3090807@cisco.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/11/2009 07:08 PM, David S. Ahern wrote: > 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. > There's pretty much nothing we can do without a core. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.