[issue30060] Crash on Py_Finalize if Py_NoSiteFlag is used

2017-04-21 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue30060] Crash on Py_Finalize if Py_NoSiteFlag is used

2017-04-13 Thread Stephen Kelly
Stephen Kelly added the comment: The issue http://bugs.python.org/issue17978 has a quite similar backtrace and there is discussion in http://bugs.python.org/issue17703#msg241412 about changing the TRASHCAN macro to access the _PyThreadState_Current directly instead of calling PyThreadStat

[issue30060] Crash on Py_Finalize if Py_NoSiteFlag is used

2017-04-13 Thread Stephen Kelly
Stephen Kelly added the comment: I found that if I build and run this code with Python 3, then I get a very different backtrace. KernelBase.dll!7ff963466142() Unknown python36_d.dll!Py_FatalError(const char * msg) Line 1457C python36_d.dll!PyEval_Acquir

[issue30060] Crash on Py_Finalize if Py_NoSiteFlag is used

2017-04-12 Thread Stephen Kelly
New submission from Stephen Kelly: When attempting to use PyImport_ImportModule("os") (or to import many other libraries), there is a crash on Py_Finalize if Py_NoSiteFlag is set. The issue appears to be the use of frozenset() as a result of importing the module. I reproduced this on Windows a