This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients BTaskaya, Michael.Felt, mark.dickinson, miss-islington, ned.deily, pablogsal, skrah, tim.peters, veky, vstinner
Date 2020-06-09.00:32:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591662734.14.0.25963445712.issue39576@roundup.psfhosted.org>
In-reply-to
Content
The 3.9 change (see #40874) works successfully on all buildbots, except for the 32-bit xlc bot which should use c99_r.

Additionally, it has been tested with the latest gcc/clang/icc/cl.exe, static analyzers and clang-tidy.

It survives brute force allocation failure tests under Valgrind and all sanitizers (ASAN + integrated LSAN, UBSAN, TSAN).


Except for one (standalone LSAN), and that is an LSAN issue:

https://github.com/google/sanitizers/issues/1257


It looks very similar to the xlc issue and was found by using a debugger, which is apparently not possible with the xlc toolchain. :-)
History
Date User Action Args
2020-06-09 00:32:14skrahsetrecipients: + skrah, tim.peters, mark.dickinson, vstinner, ned.deily, veky, Michael.Felt, pablogsal, miss-islington, BTaskaya
2020-06-09 00:32:14skrahsetmessageid: <1591662734.14.0.25963445712.issue39576@roundup.psfhosted.org>
2020-06-09 00:32:14skrahlinkissue39576 messages
2020-06-09 00:32:13skrahcreate