2011/4/30 Eric Blake <eblake@xxxxxxxxxx>:
> On 04/30/2011 05:13 AM, Matthias Bolte wrote:
>> ---
>> Âtests/.valgrind.supp | Â 58 +++++++++++++++++++++++++++++++++++++++++++------
>> Â1 files changed, 51 insertions(+), 7 deletions(-)
>>
>> diff --git a/tests/.valgrind.supp b/tests/.valgrind.supp
>> index 4af10b1..68cfa0c 100644
>> --- a/tests/.valgrind.supp
>> +++ b/tests/.valgrind.supp
>> @@ -258,14 +258,58 @@
>> Â Â Memcheck:Param
>> Â Â capget(data)
>> Â Â fun:capget
>> + Â fun:*
>> Â Â fun:capng_clear
>> + Â fun:virClearCapabilities
>> Â Â fun:__virExec
>> Â Â fun:virExecWithHook
>> - Â fun:virExec
>
>
> Makes sense.
>
>> +{
>> + Â libnlMemoryLeak1
>> + Â Memcheck:Leak
>> + Â fun:malloc
>> + Â fun:strdup
>> + Â obj:/usr/lib/libnl.so.1.1
>> +}
>
> Nice. ÂIt would be nicer if these other programs plugged their leaks,
> but doing this makes it easier to find just the libvirt leaks.
well, the world isn't perfect and for example the
VBoxNsxpNS_InitXPCOM2 suppression probably isn't a real leak, it's
just initializing tons of global stuff that later on isn't freed and
leaks on purpose. But this clutters valgrind's output massively.
> ACK.
>
Thanks, pushed.
Matthias
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list