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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
