Add more Valgrind leak report suppressions.

These leaks seem unavoidable and they are not worth reporting.

Valgrind still reports a lot of leaks that I haven't determined to either
be fixable or unavoidable.

diff --git a/tests/valgrind.supp b/tests/valgrind.supp
index b2423bab8464c189f0f3f10092f88972eb8f1146..97bb17139cce372c8b196e2f68e8c7d10105c32f 100644 (file)
--- a/tests/valgrind.supp
+++ b/tests/valgrind.supp
@@ -20,3 +20,42 @@
     ...
     fun:XML_ParseBuffer
 }
+{
+   fontconfig4
+   Memcheck:Leak
+   match-leak-kinds: possible
+   fun:calloc
+   fun:g_malloc0
+   fun:type_class_init_Wm
+   ...
+   fun:pango_fc_font_class_init
+   fun:pango_fc_font_class_intern_init
+   ...
+}
+
+# These are effectively static allocations by glib made at startup.
+{
+   g_type_register_static
+   Memcheck:Leak
+   match-leak-kinds: possible
+   ...
+   fun:g_type_register_static
+}
+{
+   g_type_register_fundamental
+   Memcheck:Leak
+   match-leak-kinds: possible
+   ...
+   fun:g_type_register_fundamental
+   ...
+}
+{
+   type_node_fundamental_new_W
+   Memcheck:Leak
+   match-leak-kinds: possible
+   ...
+   fun:type_node_fundamental_new_W
+   ...
+   fun:_dl_init
+   ...
+}