valgrind: Add another libvirt suppression

It seems as if this is just a variation on the previous libvirt
suppression.

==2042391== 61 (48 direct, 13 indirect) bytes in 1 blocks are definitely lost in
 loss record 267 of 507
==2042391==    at 0x4846464: calloc (vg_replace_malloc.c:1340)
==2042391==    by 0x54EE318: g_malloc0 (gmem.c:163)
==2042391==    by 0x5017D4C: virClassNew (virobject.c:189)
==2042391==    by 0x523CCB9: virDataTypesOnce.lto_priv.0 (datatypes.c:111)
==2042391==    by 0x4D8BE42: __pthread_once_slow (pthread_once.c:116)
==2042391==    by 0x50345E1: virOnce (virthread.c:44)
==2042391==    by 0x523CD6A: virGetConnect (datatypes.c:121)
==2042391==    by 0x51FBC1F: virConnectOpenInternal (libvirt.c:893)
==2042391==    by 0x51FCC11: virConnectOpenAuth (libvirt.c:1271)
==2042391==    by 0x4A3ECAD: guestfs_int_open_libvirt_connection.constprop.0 (li
bvirt-auth.c:224)
==2042391==    by 0x4A1D62A: launch_libvirt.lto_priv.0 (launch-libvirt.c:389)
==2042391==    by 0x4993739: guestfs_launch (launch.c:114)

(cherry picked from guestfs-tools commit 8790af0266a808c8a04927bb5039be06cbc3da54)
This commit is contained in:
Richard W.M. Jones
2023-02-20 17:46:55 +00:00
parent ede3632612
commit 4ed83ffdbe

View File

@@ -329,6 +329,16 @@
fun:virDataTypesOnce
}
{
libvirt_leak_10
Memcheck:Leak
...
fun:g_malloc0
fun:virClassNew
...
fun:virOnce
}
# FUSE leaks the per-thread context (although the code looks
# like it attempts to clean it up). In older fuse, it uses
# malloc. In newer fuse it uses calloc.