summaryrefslogtreecommitdiff
path: root/source4
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2009-11-25 17:48:29 +1100
committerAndrew Bartlett <abartlet@samba.org>2009-11-25 17:54:06 +1100
commit7de2a49f28f6d9fa26e004cf15f4756397d0ea07 (patch)
tree7f41e390e4387aa0bc34531525b28bf044ebc3e6 /source4
parent6eb262f0e8213415cfe425968c3e344a5d56e179 (diff)
downloadsamba-7de2a49f28f6d9fa26e004cf15f4756397d0ea07.tar.gz
samba-7de2a49f28f6d9fa26e004cf15f4756397d0ea07.tar.bz2
samba-7de2a49f28f6d9fa26e004cf15f4756397d0ea07.zip
s4: update valgrind suppressions for use on build farm
Diffstat (limited to 'source4')
-rw-r--r--source4/.valgrind_suppressions62
1 files changed, 62 insertions, 0 deletions
diff --git a/source4/.valgrind_suppressions b/source4/.valgrind_suppressions
index a09a4dcf7d..bf19027481 100644
--- a/source4/.valgrind_suppressions
+++ b/source4/.valgrind_suppressions
@@ -83,3 +83,65 @@
obj:/lib/ld-2.3.6.so
fun:__libc_dlsym
}
+
+#
+# Tests from valgrind-python.supp (distributed with python):
+#
+# These try and suppress these errors
+#
+
+# all tool names: Addrcheck,Memcheck,cachegrind,helgrind,massif
+{
+ ADDRESS_IN_RANGE/Invalid read of size 4
+ Memcheck:Addr4
+ fun:Py_ADDRESS_IN_RANGE
+}
+
+{
+ ADDRESS_IN_RANGE/Invalid read of size 4
+ Memcheck:Value4
+ fun:Py_ADDRESS_IN_RANGE
+}
+
+{
+ ADDRESS_IN_RANGE/Invalid read of size 8 (x86_64 aka amd64)
+ Memcheck:Value8
+ fun:Py_ADDRESS_IN_RANGE
+}
+
+{
+ ADDRESS_IN_RANGE/Conditional jump or move depends on uninitialised value
+ Memcheck:Cond
+ fun:Py_ADDRESS_IN_RANGE
+}
+
+#
+# Leaks (including possible leaks)
+# Hmmm, I wonder if this masks some real leaks. I think it does.
+# Will need to fix that.
+#
+
+{
+ Handle PyMalloc confusing valgrind (possibly leaked)
+ Memcheck:Leak
+ fun:realloc
+ fun:_PyObject_GC_Resize
+ fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+}
+
+{
+ Handle PyMalloc confusing valgrind (possibly leaked)
+ Memcheck:Leak
+ fun:malloc
+ fun:_PyObject_GC_New
+ fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+}
+
+{
+ Handle PyMalloc confusing valgrind (possibly leaked)
+ Memcheck:Leak
+ fun:malloc
+ fun:_PyObject_GC_NewVar
+ fun:COMMENT_THIS_LINE_TO_DISABLE_LEAK_WARNING
+}
+