summaryrefslogtreecommitdiff
path: root/valgrind.suppressions
diff options
context:
space:
mode:
authorLubomir Rintel <lkundrak@v3.sk>2016-11-14 19:51:24 +0100
committerLubomir Rintel <lkundrak@v3.sk>2016-11-14 20:22:23 +0100
commit172e7f100b647d35ad5de546d49c0eee3b9260cf (patch)
tree36c9e9479db65bb3214e75891fa16d0afd2c93e5 /valgrind.suppressions
parent5b3a39ddce51b680aaa157e212e61fa3f095df23 (diff)
downloadNetworkManager-172e7f100b647d35ad5de546d49c0eee3b9260cf.tar.gz
valgrind: two more gdbus suppressions
The GDBusObjectManagerClient's control proxy seems to leak some bits. Not sure why; but certainly not our fault since it's a private object and the manager object itself gets finalized.
Diffstat (limited to 'valgrind.suppressions')
-rw-r--r--valgrind.suppressions33
1 files changed, 33 insertions, 0 deletions
diff --git a/valgrind.suppressions b/valgrind.suppressions
index 50594f3007..cafde5e8a2 100644
--- a/valgrind.suppressions
+++ b/valgrind.suppressions
@@ -461,6 +461,39 @@
fun:g_bus_get_sync
}
{
+ _gdbus_f25_2
+ Memcheck:Leak
+ match-leak-kinds: definite
+ ...
+ fun:g_dbus_proxy_new_sync
+ fun:initable_init
+ fun:async_init_thread
+ fun:g_task_thread_pool_thread
+ fun:g_thread_pool_thread_proxy
+ fun:g_thread_proxy
+ fun:start_thread
+ fun:clone
+}
+{
+ _gdbusobjectmanager_f25_1
+ Memcheck:Leak
+ match-leak-kinds: definite
+ fun:malloc
+ fun:g_malloc
+ fun:g_slice_alloc
+ fun:g_slice_alloc0
+ fun:g_system_thread_new
+ fun:g_thread_new_internal
+ fun:g_thread_pool_start_thread.part.1
+ fun:g_thread_pool_start_thread
+ fun:g_thread_pool_push
+ fun:g_task_run_in_thread
+ fun:g_async_initable_real_init_async
+ fun:g_async_initable_new_valist_async
+ fun:g_async_initable_new_async
+ fun:g_dbus_object_manager_client_new_for_bus
+}
+{
_btrfs_io_clone
Memcheck:Param
ioctl(generic)