Message 145354 - Python tracker

➜

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	neologix
Recipients	bquinlan, dmalcolm, grahamd, jnoller, kristjan.jonsson, lukasz.langa, neologix, pitrou, python-dev, sandro.tosi, ysj.ray
Date	2011-10-11.17:18:59
SpamBayes Score	0.0016778038
Marked as misclassified	No
Message-id	<CAH_1eM0xAiU1+taNaGNissHvGC_y5Mwihx7pm=Vc6UP3Y0yLBg@mail.gmail.com>
In-reply-to	<CAH_1eM0MwWC6E4CqN4rYAFU9V-Lm9rYDGdKwdqyCFFadDOwrOw@mail.gmail.com>

Content
I did a quick test (calling fork() from a subinterpreter), and as expected, I couldn't reproduce the problem. So I still favor an OOM condition making pthread_setspecific bail out with ENOMEM, othe other option being a nasty libc bug. If the problem persists, please open a new issue.

I did a quick test (calling fork() from a subinterpreter), and as
expected, I couldn't reproduce the problem.
So I still favor an OOM condition making pthread_setspecific bail out
with ENOMEM, othe other option being a nasty libc bug.
If the problem persists, please open a new issue.

History
Date	User	Action	Args
2011-10-11 17:19:00	neologix	set	recipients: + neologix, bquinlan, pitrou, kristjan.jonsson, jnoller, grahamd, dmalcolm, sandro.tosi, ysj.ray, lukasz.langa, python-dev
2011-10-11 17:18:59	neologix	link	issue10517 messages
2011-10-11 17:18:59	neologix	create