[issue31200] address sanitizer build fails

STINNER Victor added the comment: FYI there is bpo-1635741 which tries to cleanup more things at Python exit. -- nosy: +vstinner ___ Python tracker ___ ___

[issue31200] address sanitizer build fails

Change by Julien Palard : -- pull_requests: +13952 pull_request: https://github.com/python/cpython/pull/13168 ___ Python tracker ___ ___

[issue31200] address sanitizer build fails

Julien Palard added the comment: Tried to reproduce it again, on master, but this does no longer segfault nor report leakages (as long as I use __INSURE__ using make -j18 profile-opt CFLAGS='-D__INSURE__') nor fail at build time. There's still a few memory warnings while running tests (subin

[issue31200] address sanitizer build fails

Julien Palard added the comment: Segfault occur in Include/object.h line 1054: #define Py_TRASHCAN_SAFE_BEGIN(op) \ do { \ PyThreadState *_tstate = PyThreadState_GET(); \ if (_tstate->trash_delete_nesting < PyTrash_UNWIND_LEVEL) { \ ⧺_tstate->trash_delete_nesting;

[issue31200] address sanitizer build fails

Julien Palard added the comment: Some (most?) of them looks to be unicode strings, and according to the very end of the main function: #ifdef __INSURE__ /* Insure++ is a memory analysis tool that aids in discovering * memory leaks and other memory problems. On Python exit, the *

[issue31200] address sanitizer build fails

Julien Palard added the comment: Are you sure you build is failing? It looks like it succeeded, if we only speak about the build. You're seeing AddressSanitizer reports because, during the build, the built python is used. Like in `./python -E -S -m sysconfig --generate-posix-vars`. So if you

[issue31200] address sanitizer build fails

New submission from Paulo Matos: Build with address sanitizer fails miserably. Configuration in Fedora 26. I attach config.log and the output of $ ../configure --with-assertions --with-lto --with-pydebug --with-address-sanitizer --disable-ipv6 $ make -j18 profile-opt -- components: Bu