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
___
Changes by Barry A. Warsaw [EMAIL PROTECTED]:
--
priority: deferred blocker - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
___
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
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
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
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
___
Changes by Jesse Noller [EMAIL PROTECTED]:
--
nosy: +jnoller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
___
___
Python-bugs-list mailing list
Changes by Gregory P. Smith [EMAIL PROTECTED]:
--
assignee: gregory.p.smith - christian.heimes
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
___
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
___
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
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
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
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
Changes by Ralf Schmitt:
--
nosy: +schmir
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
__
___
Python-bugs-list mailing list
Unsubscribe:
Christian Heimes added the comment:
Bug day task
--
nosy: +tiran
priority: - high
versions: -Python 2.4
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
__
___
Changes by Adam Olsen:
--
nosy: +rhamphoryncus
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1683
__
___
Python-bugs-list mailing list
Unsubscribe:
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
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
18 matches
Mail list logo