diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-10-08 06:56:08 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-08 06:56:08 -0700 |
| commit | 98043b4fcd80bdfa8cc2be1730fa2a4cf4950958 (patch) | |
| tree | 348f112683a6b0c606f142e2755769d12b49081d | |
| parent | 4f962ecfa1aadc45facc250841208f6dd2ce690f (diff) | |
| download | cpython-git-98043b4fcd80bdfa8cc2be1730fa2a4cf4950958.tar.gz | |
bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651)
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
(cherry picked from commit 03ab6b4fc6f59a4452756e7a3a46310ce30ec4b2)
Co-authored-by: Victor Stinner <vstinner@python.org>
| -rw-r--r-- | Misc/NEWS.d/next/Tools-Demos/2019-10-08-15-07-52.bpo-38118.pIZD6H.rst | 2 | ||||
| -rw-r--r-- | Misc/valgrind-python.supp | 11 |
2 files changed, 13 insertions, 0 deletions
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 index 0000000000..13adadb0b8 --- /dev/null +++ b/Misc/NEWS.d/next/Tools-Demos/2019-10-08-15-07-52.bpo-38118.pIZD6H.rst @@ -0,0 +1,2 @@ +Update Valgrind suppression file to ignore a false alarm in +:c:func:`PyUnicode_Decode` when using GCC builtin strcmp(). diff --git a/Misc/valgrind-python.supp b/Misc/valgrind-python.supp index bc8f77f261..38a5ea3cd2 100644 --- a/Misc/valgrind-python.supp +++ b/Misc/valgrind-python.supp @@ -283,6 +283,17 @@ 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. |