Mark Shannon <m...@hotpy.org> added the comment:
I still get quite a few failures on the main branch. It seems like ceval.c:1600 upsets the sanitizer, at least for gcc. There isn't anything wrong with that line, but as I plan to change it anyway I guess it doesn't matter: https://github.com/python/cpython/pull/26595 I plan to get the main branch passing the tests with address sanitization (at least on my machine with my gcc :) Running the tests doesn't seem to take that long (at least not compared with refleak tests). Do you think it would be it feasible to run the address sanitizer on all PRs, so that we can keep it passing? ---------- title: Likely false positive for address sanitizer after fork -> Address sanitizer (gcc version) is generating false positives _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44363> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
