1 # add valgrind suppressions for the build farm here. Get the format
2 # from the build farm log
9 obj:/lib/tls/libc-2.3.6.so
30 obj:/lib/tls/libc-2.3.6.so
39 obj:/lib/tls/libc-2.3.6.so
50 obj:/lib/tls/libc-2.3.6.so
61 obj:/lib/tls/libc-2.3.6.so
71 obj:/lib/tls/libc-2.3.6.so
82 obj:/lib/tls/libc-2.3.6.so
88 # Tests from valgrind-python.supp (distributed with python):
90 # These try and suppress these errors
93 # all tool names: Addrcheck,Memcheck,cachegrind,helgrind,massif
95 ADDRESS_IN_RANGE/Invalid read of size 4
97 fun:Py_ADDRESS_IN_RANGE
101 ADDRESS_IN_RANGE/Invalid read of size 4
103 fun:Py_ADDRESS_IN_RANGE
107 ADDRESS_IN_RANGE/Invalid read of size 8 (x86_64 aka amd64)
109 fun:Py_ADDRESS_IN_RANGE
113 ADDRESS_IN_RANGE/Conditional jump or move depends on uninitialised value
115 fun:Py_ADDRESS_IN_RANGE
119 # Leaks (including possible leaks)
120 # Hmmm, I wonder if this masks some real leaks. I think it does.
121 # Will need to fix that.
125 Handle PyMalloc confusing valgrind (possibly leaked)
128 fun:_PyObject_GC_Resize
129 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
133 Handle PyMalloc confusing valgrind (possibly leaked)
137 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
141 Handle PyMalloc confusing valgrind (possibly leaked)
144 fun:_PyObject_GC_NewVar
145 fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING