[issue31683] a stack overflow on windows in faulthandler._fatal_error()

STINNER Victor added the comment: IMHO this issue is theorical. I don't expect that anyone would call Py_FatalError() with a very long message, so I will not backport the fix to Python 2.7 and 3.6. Thanks for the bug report Oren Milman! -- resolution: -> fixed stage: patch review ->

[issue31683] a stack overflow on windows in faulthandler._fatal_error()

STINNER Victor added the comment: New changeset 8d5a3aad2f805dc0ea40829b751f58aa6c75305d by Victor Stinner in branch 'master': bpo-31683: Py_FatalError() now supports long error messages (#3878) https://github.com/python/cpython/commit/8d5a3aad2f805dc0ea40829b751f58aa6c75305d -- ___

[issue31683] a stack overflow on windows in faulthandler._fatal_error()

STINNER Victor added the comment: I proposed PR 3878 to replace alloca() with a fixed buffer of 256 bytes. -- ___ Python tracker ___ ___

[issue31683] a stack overflow on windows in faulthandler._fatal_error()

Change by STINNER Victor : -- keywords: +patch pull_requests: +3856 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-li

[issue31683] a stack overflow on windows in faulthandler._fatal_error()

New submission from Oren Milman : On my 64-bit Windows 10, the echo here would print -1073741571: python -c "import faulthandler; faulthandler._fatal_error(b'a' * 2 ** 22)" echo %errorlevel% This is code c0fd, which windbg describes as 'Stack overflow'. This happens because Py_FatalError() (