<[email protected]>; 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 <mcheck.c>, 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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
