]> granicus.if.org Git - python/commitdiff
bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651)
authorVictor Stinner <vstinner@python.org>
Tue, 8 Oct 2019 13:42:17 +0000 (15:42 +0200)
committerGitHub <noreply@github.com>
Tue, 8 Oct 2019 13:42:17 +0000 (15:42 +0200)
Valgrind emits "Conditional jump or move depends on uninitialised
value(s)" false alarms on GCC builtin strcmp() function. The GCC code
is correct.

Valgrind bug: https://bugs.kde.org/show_bug.cgi?id=264936

Misc/NEWS.d/next/Tools-Demos/2019-10-08-15-07-52.bpo-38118.pIZD6H.rst [new file with mode: 0644]
Misc/valgrind-python.supp

diff --git a/Misc/NEWS.d/next/Tools-Demos/2019-10-08-15-07-52.bpo-38118.pIZD6H.rst b/Misc/NEWS.d/next/Tools-Demos/2019-10-08-15-07-52.bpo-38118.pIZD6H.rst
new file mode 100644 (file)
index 0000000..13adadb
--- /dev/null
@@ -0,0 +1,2 @@
+Update Valgrind suppression file to ignore a false alarm in
+:c:func:`PyUnicode_Decode` when using GCC builtin strcmp().
index bc8f77f261a805498bc9d36a2e5c4b1e520cb75f..38a5ea3cd2b828f8625448ccffbd23b376b12efc 100644 (file)
    fun:rl_initialize
 }
 
+# Valgrind emits "Conditional jump or move depends on uninitialised value(s)"
+# false alarms on GCC builtin strcmp() function. The GCC code is correct.
+#
+# Valgrind bug: https://bugs.kde.org/show_bug.cgi?id=264936
+{
+   bpo-38118: Valgrind emits false alarm on GCC builtin strcmp()
+   Memcheck:Cond
+   fun:PyUnicode_Decode
+}
+
+
 ###
 ### These occur from somewhere within the SSL, when running
 ###  test_socket_sll.  They are too general to leave on by default.