Am 29.02.2012 17:19, schrieb Michael S. Tsirkin:
Here's a full report of possible leaks:
Any idea? I am invedtigating.
Hi Michael,
try valgrind with --track-origins=yes. It costs some memory, but
improves diagnostics not only for memory leaks.
Most important are the leaks marked with "definit
Here's a full report of possible leaks:
Any idea? I am invedtigating.
==21745== 8 bytes in 1 blocks are definitely lost in loss record 105 of 856
==21745==at 0x4A05FDE: malloc (vg_replace_malloc.c:236)
==21745==by 0x24D4C5: malloc_and_trace (vl.c:2156)
==21745==by 0x506334D: ??? (in /l
