[issue26102] access violation in PyErrFetch if tcur==null in PyGILState_Release

STINNER Victor added the comment: Good news: it looks like I fixed the Py_FatalError() bug in the issue #26558. Py_FatalError() can again be called with the GIL released. The bug was introduced in Python 3.0. Since your issue is a bug in your code and that Py_FatalError() was fixed, I close

[issue26102] access violation in PyErrFetch if tcur==null in PyGILState_Release

Changes by SilentGhost : -- nosy: +benjamin.peterson ___ Python tracker ___ ___

[issue26102] access violation in PyErrFetch if tcur==null in PyGILState_Release

New submission from Christian Berger: I've been messing with PyGILState_... handling for my embedded python interpreter and came across this issue: code in PyGILState_Release: PyThreadState *tcur = (PyThreadState *)PyThread_get_key_value(