[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

STINNER Victor added the comment: Thanks for the report. This issue should now be fixed. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

Roundup Robot added the comment: New changeset 689092296ad3 by Victor Stinner in branch '3.4': Issue #23433: Fix faulthandler._stack_overflow() https://hg.python.org/cpython/rev/689092296ad3 -- nosy: +python-dev ___ Python tracker

[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

Matěj Stuchlík added the comment: FWIW with your patch all the tests pass on Fedora rawhide in Koji [1], whereas before the x86_64 build would hang [2]. If you want to do some more testing, you can download the rpms from [1]. :) [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=8894494 [2

[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

Changes by Matěj Stuchlík : -- nosy: +sYnfo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

STINNER Victor added the comment: faulthandler._stack_overflow() is written to crash. The comparison on stack pointers is just here to avoid an unlimited loop. A stack of 100 MB is something really large. I never seen an OS where faulthandler._stack_overflow() doesn't crash yet. Here is a pat

[issue23433] undefined behaviour in faulthandler.c, exposed by GCC 5

New submission from Matthias Klose: richi: https://github.com/nemomobile-packages/python3/blob/master/Modules/faulthandler.c#L903 richi: LD_LIBRARY_PATH=/builddir/build/BUILD/Python-3.4.2/build/debug/ /builddir/build/BUILD/Python-3.4.2/build/debug/python -E -c 'import faulthandler; faulthan