From: Reuben Thomas <rrt@sc3d.org>
Date: Mon, 29 Jan 2018 14:41:08 +0000 (+0000)
Subject: Add more suppressions
X-Git-Tag: v3.7~23
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c080c839df9af286f8c153e7d4849b51898cb8e0;p=recode

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 53cabca..7021766 100644
--- 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
 }
 
 #