From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:37169)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1UP9fG-0000JD-Cd
	for qemu-devel@nongnu.org; Mon, 08 Apr 2013 06:51:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1UP9f6-0000Qw-Kn
	for qemu-devel@nongnu.org; Mon, 08 Apr 2013 06:51:06 -0400
Received: from mail-wg0-f49.google.com ([74.125.82.49]:52067)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1UP9f6-0000Qi-6E
	for qemu-devel@nongnu.org; Mon, 08 Apr 2013 06:50:56 -0400
Received: by mail-wg0-f49.google.com with SMTP id e11so5485588wgh.28
	for <qemu-devel@nongnu.org>; Mon, 08 Apr 2013 03:50:55 -0700 (PDT)
Date: Mon, 8 Apr 2013 12:50:52 +0200
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20130408105052.GC12076@stefanha-thinkpad.redhat.com>
References: <D3E216785288A145B7BC975F83A2ED103FE154C1@szxeml556-mbx.china.huawei.com>
	<20130405063456.GA27569@stefanha-thinkpad.redhat.com>
	<D3E216785288A145B7BC975F83A2ED103FE16528@szxeml556-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D3E216785288A145B7BC975F83A2ED103FE16528@szxeml556-mbx.china.huawei.com>
Subject: Re: [Qemu-devel]
 =?utf-8?b?562U5aSNOiAgcWVtdSBjcmFzaGVkIHdoZW4gc3Rh?=
 =?utf-8?q?rting_vm=28kvm=29_with_vnc_connect?=
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Zhanghaoyu (A)" <haoyu.zhang@huawei.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>, kvm list <kvm@vger.kernel.org>, Marcelo Tosatti <mtosatti@redhat.com>, Luonengjun <luonengjun@huawei.com>, qemu-devel <qemu-devel@nongnu.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Zanghongyong <zanghongyong@huawei.com>, Zhanghuanzhong <zhanghuanzhong@huawei.com>

On Sun, Apr 07, 2013 at 04:58:07AM +0000, Zhanghaoyu (A) wrote:
> >> I start a kvm VM with vnc(using the zrle protocol) connect, sometimes qemu program crashed during starting period, received signal SIGABRT.
> >> Trying about 20 times, this crash may be reproduced.
> >> I guess the cause memory corruption or double free.
> >
> > Which version of QEMU are you running?
> > 
> > Please try qemu.git/master.
> > 
> > Stefan
> 
> I used the QEMU download from qemu.git (http://git.qemu.org/git/qemu.git).

Great, thanks!  Can you please post a backtrace?

The easiest way is:

  $ ulimit -c unlimited
  $ qemu-system-x86_64 -enable-kvm -m 1024 ...
  ...crash...
  $ gdb -c qemu-system-x86_64.core
  (gdb) bt

Depending on how your system is configured the core file might have a
different filename but there should be a file name *core* the current
working directory after the crash.

The backtrace will make it possible to find out where the crash
occurred.

Thanks,
Stefan