[Python-Dev] _PyThreadState_Current (original) (raw)
Maciej Fijalkowski fijall at gmail.com
Mon Jan 18 15:32:28 EST 2016
- Previous message (by thread): [Python-Dev] _PyThreadState_Current
- Next message (by thread): [Python-Dev] _PyThreadState_Current
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
seems to work thanks.
That said, I would love to have PyThreadState_Get equivalent that would let me handle the NULL.
On Mon, Jan 18, 2016 at 9:31 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:
Good point
On Mon, Jan 18, 2016 at 9:25 PM, Victor Stinner <victor.stinner at gmail.com> wrote: Hum, you can try to lie and define PyBUILDCORE?
Victor 2016-01-18 21:18 GMT+01:00 Maciej Fijalkowski <fijall at gmail.com>: Hi
change in between 3.5.0 and 3.5.1 (hiding PyThreadStateCurrent and pyatomic.h) broke vmprof. The problem is that as a profile, vmprof can really encounter PyThreadStateCurrent being null, while crashing an interpreter is a bit not ideal in this case. Any chance, a) PyThreadStateCurrent 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 at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com
- Previous message (by thread): [Python-Dev] _PyThreadState_Current
- Next message (by thread): [Python-Dev] _PyThreadState_Current
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]