[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-12-13 Thread Martin v. Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: Committed fork-thread-patch-2 as r67736 into 2.5 branch. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1683 ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-12-03 Thread Barry A. Warsaw
Changes by Barry A. Warsaw [EMAIL PROTECTED]: -- priority: deferred blocker - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-30 Thread Barry A. Warsaw
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Since this is a Python 2.5.3 issue, I'm lowering to deferred blocker until after 3.0 and 2.6.1 are released. -- nosy: +barry priority: release blocker - deferred blocker ___ Python tracker [EMAIL

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-29 Thread Christian Heimes
Christian Heimes [EMAIL PROTECTED] added the comment: I was wrong and the patch is right. Something is wrong in multiprocessings connection_recvbytes_into() function for the old buffer protocol. Somehow PyArg_ParseTuple(args, w#| ...) fucks up the process' memory. Martin, are you fine with the

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-28 Thread Christian Heimes
Christian Heimes [EMAIL PROTECTED] added the comment: The fix is required to run multiprocessing on Python 2.4 and 2.5, see #4451. I suggest we fix the issue in 2.5.3. The fork-thread-patch-2 patch doesn't work on Python 2.5. I'm getting a segfault on my system: test_connection

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-28 Thread Benjamin Peterson
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- versions: -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-28 Thread Jesse Noller
Changes by Jesse Noller [EMAIL PROTECTED]: -- nosy: +jnoller ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 ___ ___ Python-bugs-list mailing list

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-11-28 Thread Gregory P. Smith
Changes by Gregory P. Smith [EMAIL PROTECTED]: -- assignee: gregory.p.smith - christian.heimes ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-06-12 Thread Benjamin Peterson
Benjamin Peterson [EMAIL PROTECTED] added the comment: I applied this in r64212. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-06-11 Thread Gregory P. Smith
Gregory P. Smith [EMAIL PROTECTED] added the comment: we need this in before 2.6 is released. -- assignee: - gregory.p.smith nosy: +gregory.p.smith priority: high - critical ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-06-11 Thread Benjamin Peterson
Benjamin Peterson [EMAIL PROTECTED] added the comment: Gregory, go ahead and apply and see if can stop the hell in the buildbots. -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-06-11 Thread Adam Olsen
Adam Olsen [EMAIL PROTECTED] added the comment: Updated version of roudkerk's patch. Adds the new function to pythread.h and is based off of current trunk. Note that Parser/intrcheck.c isn't used on my box, so it's completely untested. roudkerk's original analysis is correct. The TLS is

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-06-11 Thread Adam Olsen
Adam Olsen [EMAIL PROTECTED] added the comment: Incidentally, it doesn't seem necessary to reinitialize the lock. Posix duplicates the lock, so if you hold it when you fork your child will be able to unlock it and use it as normal. Maybe there's some non-Posix behaviour or something even more

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-03-07 Thread Ralf Schmitt
Changes by Ralf Schmitt: -- nosy: +schmir __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-01-08 Thread Christian Heimes
Christian Heimes added the comment: Bug day task -- nosy: +tiran priority: - high versions: -Python 2.4 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 __ ___

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-01-08 Thread Adam Olsen
Changes by Adam Olsen: -- nosy: +rhamphoryncus __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2008-01-06 Thread roudkerk
roudkerk added the comment: The included patch against python2.51 fixes the problem for me. -- versions: +Python 2.6, Python 3.0 Added file: http://bugs.python.org/file9076/fork-thread-patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1683

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

2007-12-21 Thread roudkerk
New submission from roudkerk: I got a report that one of the tests for processing (http://cheeseshop.python.org/pypi/processing) was failing with Fatal Python error: Invalid thread state for this thread when run with a debug interpreter. This appears to be caused by the interaction