[issue31857] Make the behavior of USE_STACKCHECK deterministic

2020-03-16 Thread STINNER Victor
Change by STINNER Victor : -- pull_requests: +18384 pull_request: https://github.com/python/cpython/pull/19034 ___ Python tracker ___

[issue31857] Make the behavior of USE_STACKCHECK deterministic

2019-11-04 Thread STINNER Victor
STINNER Victor added the comment: This issue added this FIXME: /* Due to the macros in which it's used, _Py_CheckRecursionLimit is in the stable ABI. It should be removed therefrom when possible. */ FYI I proposed PR 17046 to fix it ;-) -- nosy: +vstinner

[issue31857] Make the behavior of USE_STACKCHECK deterministic

2017-10-26 Thread Benjamin Peterson
Benjamin Peterson added the comment: New changeset 1896793520a49a6f97ae360c0b288967e56b005e by Benjamin Peterson (pdox) in branch 'master': bpo-31857: Make the behavior of USE_STACKCHECK deterministic (#4098)

[issue31857] Make the behavior of USE_STACKCHECK deterministic

2017-10-26 Thread Benjamin Peterson
Change by Benjamin Peterson : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31857] Make the behavior of USE_STACKCHECK deterministic

2017-10-23 Thread pdox
Change by pdox : -- keywords: +patch pull_requests: +4069 stage: -> patch review ___ Python tracker ___

[issue31857] Make the behavior of USE_STACKCHECK deterministic

2017-10-23 Thread pdox
New submission from pdox : USE_STACKCHECK is a Windows-only feature which provides additional safety against C stack overflow by periodically calling PyOS_CheckStack to determine whether the current thread is too close to the end of the stack. The way USE_STACKCHECK ensures