From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leszek Urbanski Subject: Re: [PATCH] block: Free iovec arrays allocated by multiwrite_merge() Date: Wed, 21 Apr 2010 22:13:40 +0200 Message-ID: <20100421201340.GB26113@moo.pl> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Cc: kvm@vger.kernel.org To: Ryan Harper Return-path: Received: from moo.pl ([217.149.240.132]:33655 "EHLO moo.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754073Ab0DUUNp (ORCPT ); Wed, 21 Apr 2010 16:13:45 -0400 Content-Disposition: inline In-Reply-To: <20100421200358.GH24351@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: <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. -- Leszek "Tygrys" Urbanski, SCSA, SCNA "Unix-to-Unix Copy Program;" said PDP-1. "You will never find a more wretched hive of bugs and flamers. We must be cautious." -- DECWARS http://cygnus.moo.pl/ -- Cygnus High Altitude Balloon