Message254739
The interpreter isn't initialized, so calling PyErr_Format in a release build segfaults when it tries to dereference a NULL PyThreadState. OTOH, a debug build should call PyThreadState_Get, which in this case calls Py_FatalError and aborts the process. Unfortunately 3.5.0+ debug builds don't call PyThreadState_Get due to the fix for issue 25150.
> the possibility of other exceptions being raised early in the
> initialization sequence remains a potential problem.
PEP 432 proposes a pre-initialization phase that sets a valid Python thread state. |
|
Date |
User |
Action |
Args |
2015-11-16 16:32:54 | eryksun | set | recipients:
+ eryksun, ncoghlan, itaibn |
2015-11-16 16:32:54 | eryksun | set | messageid: <1447691574.09.0.925595204356.issue25631@psf.upfronthosting.co.za> |
2015-11-16 16:32:54 | eryksun | link | issue25631 messages |
2015-11-16 16:32:53 | eryksun | create | |
|