From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJNiL-00054h-66 for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:52:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJNiG-00053I-P2 for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:52:32 -0500 Received: from [199.232.76.173] (port=49061 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJNiG-000537-Lp for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:52:28 -0500 Received: from moutng.kundenserver.de ([212.227.126.187]:56466) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJNiG-0006XK-6J for qemu-devel@nongnu.org; Sat, 12 Dec 2009 03:52:28 -0500 Message-ID: <4B2359BB.9070703@mail.berlios.de> Date: Sat, 12 Dec 2009 09:52:11 +0100 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT References: <4B227C7E.3090807@cisco.com> In-Reply-To: <4B227C7E.3090807@cisco.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 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.