diff options
author | Olli Salli <ollisal@gmail.com> | 2010-12-05 23:47:48 +0200 |
---|---|---|
committer | Olli Salli <ollisal@gmail.com> | 2010-12-05 23:47:48 +0200 |
commit | ef771926ec91d0229f9a88d641b0c251ba2f83bc (patch) | |
tree | b894c2ad284f7ef2268dd0409f89570d7222b234 | |
parent | ca611d14e56c876f4799639be1b52c768dc3cec9 (diff) |
Make the QDBus not calling dbus_shutdown suppression even less specific
-rw-r--r-- | tools/tp-qt4-tests.supp | 19 |
1 files changed, 6 insertions, 13 deletions
diff --git a/tools/tp-qt4-tests.supp b/tools/tp-qt4-tests.supp index 640593fa..c8972f2c 100644 --- a/tools/tp-qt4-tests.supp +++ b/tools/tp-qt4-tests.supp @@ -1,20 +1,13 @@ -# QDBus doesn't call dbus_shutdown, so some D-Bus internal data structures are leaked +# QDBus doesn't call dbus_shutdown, so some D-Bus internal data structures are leaked. +# We never call any low-level dbus message creation functions ourselves - if there are leaks, +# they're either caused by not calling dbus_shutdown, QDBus bugs or libdbus bugs - neither of which +# are our problem. { Initial session bus registration message Memcheck:Leak - ... - fun:dbus_bus_register - fun:internal_bus_get - fun:_ZN15QDBusConnection12connectToBusENS_7BusTypeERK7QString -} - -{ - Match rule registration messages - Memcheck:Leak - ... - fun:dbus_message_new_method_call - fun:dbus_bus_add_match + fun:malloc + fun:dbus_message_new_empty_header } # The conference test CM channel object leaks some crazy GValue boxed data which I don't have the |