[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

STINNER Victor added the comment: Ok, the issue has been fixed in 3.7, 3.8 and master branches. Ensure that you use Valgrind with Misc/valgrind.supp. Example: $ echo|PYTHONMALLOC=malloc valgrind --suppressions=Misc/valgrind-python.supp ./python Lib/tokenize.py (...) ==12923== ERROR SUMMARY:

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

miss-islington added the comment: New changeset 98043b4fcd80bdfa8cc2be1730fa2a4cf4950958 by Miss Islington (bot) in branch '3.7': bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651) https://github.com/python/cpython/commit/98043b4fcd80bdfa8cc2be1730fa2a4cf4950958 ---

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

Change by miss-islington : -- pull_requests: +16237 pull_request: https://github.com/python/cpython/pull/16654 ___ Python tracker ___ __

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

miss-islington added the comment: New changeset 364532fb4962991d278da6470c3aec4e443e533d by Miss Islington (bot) in branch '3.8': bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651) https://github.com/python/cpython/commit/364532fb4962991d278da6470c3aec4e443e533d ---

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

Change by miss-islington : -- pull_requests: +16235 pull_request: https://github.com/python/cpython/pull/16652 ___ Python tracker ___ __

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

Change by miss-islington : -- pull_requests: +16236 pull_request: https://github.com/python/cpython/pull/16653 ___ Python tracker ___ __

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

STINNER Victor added the comment: New changeset 03ab6b4fc6f59a4452756e7a3a46310ce30ec4b2 by Victor Stinner in branch 'master': bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651) https://github.com/python/cpython/commit/03ab6b4fc6f59a4452756e7a3a46310ce30ec4b2 --

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

STINNER Victor added the comment: It seems like Python 2.7 is not affected. -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

Change by STINNER Victor : -- keywords: +patch pull_requests: +16234 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/16651 ___ Python tracker _

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

STINNER Victor added the comment: The valgrind false alarm on GCC builtin strcmp() has been reported to the Valgrind bug tracker in 2011, with an update in 2012 and... nothing :-( https://bugs.kde.org/show_bug.cgi?id=264936 curl worked around the issue by disabling valgrind on the impacted te

[issue38118] Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()

STINNER Victor added the comment: > ==6832==at 0x4D87E9: PyUnicode_Decode (unicodeobject.c:3395) This warning is a false alarm: the GCC builtin strcmp() function seems to read past the NUL byte. When recompiling Python with -fno-builtin GCC option, the warning is gone. The valgrind warn