From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: qemu-kvm crash with "double free or corruption"
Date: Thu, 24 Mar 2011 14:03:10 +0200
Message-ID: <20110324120310.GD32408@redhat.com>
References: <loom.20110324T124830-43@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Conor Murphy <conor_murphy_virt@hotmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:14954 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752757Ab1CXMDM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 24 Mar 2011 08:03:12 -0400
Content-Disposition: inline
In-Reply-To: <loom.20110324T124830-43@post.gmane.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Thu, Mar 24, 2011 at 11:55:06AM +0000, Conor Murphy wrote:
> Hi,
> 
> I'm trying to write a vioblk driver for Solaris. I've gotten it to the point
> where the devices are visible to Solaris and can create and FDISK partition
> table and label it.
> 
> However, when I try an use newfs to create a filesystem, the VM crashes with the
> following in the log
> 
> *** glibc detected *** /usr/bin/qemu-kvm: double free or corruption (!prev):
> 0x00007fda4c000a00 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x3d6da76d63]
> /usr/bin/qemu-kvm[0x43d6ce]
> /lib64/libpthread.so.0[0x3d6e206ccb]
> /lib64/libc.so.6(clone+0x6d)[0x3d6dae0c2d]
> 
> I'm using qemu-kvm-0.14.0-4.fc14.x86_64
> 
> Any suggestions on how to debug this?
> 
Compile with debug symbols without optimization and run inside gdb to
get better back trace.

--
			Gleb.