On 04/21/2010 10:53 AM, Leszek Urbanski wrote:
<08761DCA-B8FA-41C8-A839-52E09BC06824@xxxxxxx>; from Alexander Graf on Wed, Apr 21, 2010 at 00:51:21 +0200
-039b9000-5ccd0000 rw-p 00000000 00:00 0
+039b9000-65803000 rw-p 00000000 00:00 0
(a heap leak?)
I'm willing to debug further. The problem is 100% reproducible.
Certainly something malloc()'ed. It'd be great to send this through valgrind. Thanks to KVM the guest still runs natively, so the slowdown isn't _that_ bug through it. I'm also not a valgrind expert, but IIRC there was a separate memory allocation module.
Unfortunately, KVM guests with virtio won't even finish booting with valgrind.
The guest's kernel complains about I/O errors in the first sectors of the
virtio root device.
You can try glibc's malloc tracing, see libc's mtrace().
--
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
