Add more suppressions

Use of subprocess module seems to tickle Valgrind, so activate some existing
leak suppressions and add some more.

diff --git a/tests/valgrind-python.supp b/tests/valgrind-python.supp
index 53cabcade462836b884fbb31bf03a69fbcd19b19..702176646b494a6578d199e487c6a01cbc028ccd 100644 (file)
--- a/tests/valgrind-python.supp
+++ b/tests/valgrind-python.supp
@@ -67,7 +67,7 @@
    Memcheck:Leak
    fun:malloc
    fun:PyThread_allocate_lock
-   fun:PyEval_InitThreads
+#   fun:PyEval_InitThreads
 }
 
 {
@@ -100,7 +100,7 @@
    Memcheck:Leak
    fun:realloc
    fun:_PyObject_GC_Resize
-   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+#   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
 }
 
 {
@@ -108,7 +108,7 @@
    Memcheck:Leak
    fun:malloc
    fun:_PyObject_GC_New
-   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+#   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
 }
 
 {
@@ -116,7 +116,16 @@
    Memcheck:Leak
    fun:malloc
    fun:_PyObject_GC_NewVar
-   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+#   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+}
+
+
+{
+   Handle PyMalloc confusing valgrind (possibly leaked)
+   Memcheck:Leak
+   fun:malloc
+   fun:PyObject_Malloc
+#   fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
 }
 
 #