[issue43662] test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 on x86-64 and s390x with GCC 4.8.5 and LTO

STINNER Victor added the comment: This issue should be fixed by: commit 92a02c1f7e2dcdc62913a4236589e7e5d96172b9 Author: Pablo Galindo Date: Tue Mar 30 00:24:49 2021 +0100 Fix tokenizer error when raw decoding null bytes (GH-25080) The fix is the usage of strlen() instead of

[issue43662] test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 on x86-64 and s390x with GCC 4.8.5 and LTO

STINNER Victor added the comment: It's a buffer overflow, or at least a crash related to uninitialized bytes. See: https://github.com/python/cpython/pull/25080#issuecomment-809752737 -- ___ Python tracker

[issue43662] test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 on x86-64 and s390x with GCC 4.8.5 and LTO

STINNER Victor added the comment: vstinner@python-builder-rhel7$ echo|PYTHONMALLOC=malloc valgrind ./python Tools/scripts/reindent.py ==26374== Memcheck, a memory error detector ==26374== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==26374== Using Valgrind-3.15.0 and

[issue43662] test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 on x86-64 and s390x with GCC 4.8.5 and LTO

STINNER Victor added the comment: s390x RHEL7 LTO 3.x: builds 921, 924 and 925 failed with test_reindent_file_with_bad_encoding(). -- title: test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 with LTO -> test_tools: test_reindent_file_with_bad_encoding() fails RHEL7 on