On 04/21/2010 11:13 PM, Leszek Urbanski wrote:
<20100421200358.GH24351@xxxxxxxxxx>; 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.
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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
