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-08.10:52:20
SpamBayes Score 7.0530803e-12
Marked as misclassified No
Message-id <>
In-reply-to <>

> Did anyone test this fix for case of fork() being called from Python sub interpreter?

Not specifically, unless it's part of the test suite.
Anyway, unless this problem is systematic - which I doubt - it
probably wouldn't have helped.

> Getting a report of fork() failing in sub interpreters under mod_wsgi that may be caused by this change. Still investigating.
> Specifically throwing up error:
>  Couldn't create autoTLSkey mapping

If you can, try strace or instrument the code (perror() should be
enough) to see why it's failing.
pthread_setspecific() can fail with:
- EINVAL, if the TLS key is invalid (which would be strange since we
call pthread_key_delete()/pthread_key_create() just before)
- or ENOMEM, if you run out of memory/address space

The later seems much more likely (e.g. if many child processes and
subinterpreters are created).
BTW, if this is a bug report from someone else, tell him to post here,
it'll be easier.
And we don't byte :-)
Date User Action Args
2011-10-08 10:52:21neologixsetrecipients: + neologix, bquinlan, pitrou, kristjan.jonsson, jnoller, grahamd, dmalcolm, sandro.tosi, ysj.ray, lukasz.langa, python-dev
2011-10-08 10:52:21neologixlinkissue10517 messages
2011-10-08 10:52:20neologixcreate