From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJN3F-0007de-Gt for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:10:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJN3A-0007bb-Kr for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:10:04 -0500 Received: from [199.232.76.173] (port=47236 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJN3A-0007bV-FU for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:10:00 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11019) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJN39-0002vW-Ut for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:10:00 -0500 Message-ID: <4B234FD2.8080608@redhat.com> Date: Sat, 12 Dec 2009 10:09:54 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4B227C7E.3090807@cisco.com> In-Reply-To: <4B227C7E.3090807@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Qemu terminating with SIGABRT List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "David S. Ahern" Cc: qemu-devel@nongnu.org, kvm-devel 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.