This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steveire
Recipients steveire
Date 2017-04-13.10:54:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492080886.69.0.842979683291.issue30060@psf.upfronthosting.co.za>
In-reply-to
Content
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 PyThreadState_Get (which is fatal for a nullptr). The very next thing the TRASHCAN macro does is check if the thread state is nullptr in a non-fatal way. 

Is there a reason not to apply that patch?
History
Date User Action Args
2017-04-13 10:54:46steveiresetrecipients: + steveire
2017-04-13 10:54:46steveiresetmessageid: <1492080886.69.0.842979683291.issue30060@psf.upfronthosting.co.za>
2017-04-13 10:54:46steveirelinkissue30060 messages
2017-04-13 10:54:46steveirecreate