Imported Upstream version 0.6.0.12upstream/0.6.0.12

1 files changed, 75 insertions, 30 deletions

diff --git a/misc/coding_helpers/python.supp b/misc/coding_helpers/python.supp
index a2e37bb..102e2ec 100644
--- a/misc/coding_helpers/python.supp
+++ b/misc/coding_helpers/python.supp
@@ -1,33 +1,78 @@
-#
-# This is a valgrind suppression file that should be used when using valgrind.
-#
-# ---------------------------------------------------------------------------
-# Debian note:
-# The file Misc/valgrind-python.supp is placed in an modified form into the
-# directory /usr/lib/valgrind as python.supp. There's no need to to add it
-# with the --suppressions option.
-# The unmodified file is found in /usr/share/doc/python2.4/
-#
-# The python2.4-dbg build has been compiled with -DPy_USING_MEMORY_DEBUGGER
-# so you can safely comment out the suppressions for PyObject_Free and
-# PyObject_Realloc.
-# ---------------------------------------------------------------------------
-
-#  Here's an example of running valgrind:
-#
-#	cd python/dist/src
-#	valgrind --tool=memcheck --suppressions=Misc/valgrind-python.supp \
-#		./python -E -tt ./Lib/test/regrtest.py -u bsddb,network
-#
-# You must edit Objects/obmalloc.c and uncomment Py_USING_MEMORY_DEBUGGER
-# to use the preferred suppressions with Py_ADDRESS_IN_RANGE.
-#
-# If you do not want to recompile Python, you can uncomment
-# suppressions for PyObject_Free and PyObject_Realloc.
-#
-# See /usr/share/doc/python2.4/README.valgrind for more information.
-
-# all tool names: Addrcheck,Memcheck,cachegrind,helgrind,massif
+# generated on buildbot.rubenkerkhof.com, which had, according to Ruben
+# Fedora's package "openssl-1.0.1-0.1.beta2.fc17.x86_64"
+{
+   buildbot.rubenkerkhof.com cond fips openssl 1
+   Memcheck:Cond
+   fun:bcmp
+   fun:fips_get_entropy
+   fun:FIPS_drbg_instantiate
+   fun:RAND_init_fips
+   fun:OPENSSL_init_library
+   fun:SSL_library_init
+   fun:init_hashlib
+}
+
+{
+   buildbot.rubenkerkhof.com cond fips openssl 2
+   Memcheck:Cond
+   fun:fips_get_entropy
+   fun:FIPS_drbg_instantiate
+   fun:RAND_init_fips
+   fun:OPENSSL_init_library
+   fun:SSL_library_init
+   fun:init_hashlib
+}
+
+{
+   buildbot.rubenkerkhof.com val _x86_64_AES_encrypt_compact
+   Memcheck:Value8
+   fun:_x86_64_AES_encrypt_compact
+   fun:AES_encrypt
+}
+
+# generated on buildbot.rubenkerkhof.com Jakub Jellinek guessed that this was
+# a false alarm due to index knowing that pointers are 4-byte aligned and
+# valgrind not taking that into account:
+# https://bugzilla.redhat.com/show_bug.cgi?id=159701
+{
+   buildbot.rubenkerkhof.com cond index
+   Memcheck:Cond
+   fun:index
+   fun:expand_dynamic_string_token
+   fun:_dl_map_object
+   fun:map_doit
+   fun:_dl_catch_error
+}
+
+# generated on luther sid
+# e.g. https://tahoe-lafs.org/buildbot-pycryptopp/builders/luther%20sid/builds/38/steps/double%20load%20valgrind/logs/valgrind
+{
+   luther sid addr4 realloc
+   Memcheck:Addr4
+   fun:PyObject_Realloc.part.0.20700
+}
+
+{
+   luther sid cond realloc
+   Memcheck:Cond
+   fun:PyObject_Realloc.part.0.20700
+}
+
+{
+   luther sid value4 realloc
+   Memcheck:Value4
+   fun:PyObject_Realloc.part.0.20700
+}
+
+# glibc was apparently changed to avoid this: http://sources.redhat.com/bugzilla/show_bug.cgi?id=4306
+{
+   use (not really, according to Ulrich Drepper) of uninitailised bytes by glibc in utimes()
+   Memcheck:Param
+   utimes(tvp[1])
+   fun:utimes
+   obj:/usr/lib/libpython2.4.so.1.0
+}
+
 {
    ADDRESS_IN_RANGE/Invalid read of size 4
    Memcheck:Addr4