From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] block: Free iovec arrays allocated by multiwrite_merge() Date: Sun, 25 Apr 2010 15:36:23 +0300 Message-ID: <4BD43747.1070403@redhat.com> References: <20100421143209.GC24351@us.ibm.com> <1271874464-3021-1-git-send-email-stefanha@linux.vnet.ibm.com> <20100421183536.GG24351@us.ibm.com> <20100421195928.GA26113@moo.pl> <20100421200358.GH24351@us.ibm.com> <20100421201340.GB26113@moo.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: Ryan Harper , kvm@vger.kernel.org To: Leszek Urbanski Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28859 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752478Ab0DYMg2 (ORCPT ); Sun, 25 Apr 2010 08:36:28 -0400 In-Reply-To: <20100421201340.GB26113@moo.pl> Sender: kvm-owner@vger.kernel.org List-ID: On 04/21/2010 11:13 PM, Leszek Urbanski wrote: > <20100421200358.GH24351@us.ibm.com>; from Ryan Harper on Wed, Apr 21, 2010 at 15:03:58 -0500 > > >>> Debugging with mtrace() also pointed to the iovec code as the culprit. >>> >> I've not used mtrace before, could you dump your command invocation for >> the list? I know other's would be glad to see an example with kvm >> > #include, put mtrace() and muntrace() around the code in main() > in vl.c > > export MALLOC_TRACE=/some/file > > then run qemu with your usual options. After powering off the guest, > run "mtrace /path/to/qemu-binary /some/file" - it's a perl script that makes > the output more human readable. > > It's a little tricky, though - remember that it will see most allocations > occurring in qemu-malloc.c - it only traces explicit glibc malloc() calls. > Does it show only the immediate caller, without a complete stack trace? If so, that sucks. -- error compiling committee.c: too many arguments to function