From: Juan Quintela Subject: Re: Qemu terminating with SIGABRT Date: Fri, 11 Dec 2009 19:11:25 +0100 Message-ID: References: <4B227C7E.3090807@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: qemu-devel@nongnu.org, kvm-devel To: "David S. Ahern" Return-path: Received: from trasno.trasno.org ([91.117.31.254]:35929 "EHLO trasno.trasno.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758866AbZLKTLY (ORCPT ); Fri, 11 Dec 2009 14:11:24 -0500 In-Reply-To: <4B227C7E.3090807@cisco.com> (David S. Ahern's message of "Fri, 11 Dec 2009 10:08:14 -0700") Sender: kvm-owner@vger.kernel.org List-ID: "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. My experience with abort() was with code calling qemu_malloc(0). (*) Not sure if this is the problem that you are seing, but this is as good guess as anyother one. Later, Juan. (*): Please, not atother qemu_malloc(0) flame, please.