[Python-Dev] _PyThreadState_Current
Maciej Fijalkowski fijall at gmail.com
Mon Jan 18 15:18:28 EST 2016
Hi change in between 3.5.0 and 3.5.1 (hiding _PyThreadState_Current and pyatomic.h) broke vmprof. The problem is that as a profile, vmprof can really encounter _PyThreadState_Current being null, while crashing an interpreter is a bit not ideal in this case. Any chance, a) _PyThreadState_Current can be restored in visibility? b) can I get a better API to get it in case it can be NULL, but also in 3.5 (since it works in 3.5.0 and breaks in 3.5.1) Cheers, fijal
More information about the Python-Dev mailing list