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 christian.heimes
Recipients Rhamphoryncus, benjamin.peterson, christian.heimes, gregory.p.smith, roudkerk, schmir
Date 2008-11-28.15:15:31
SpamBayes Score 1.9229526e-07
Marked as misclassified No
Message-id <1227885333.71.0.671829505716.issue1683@psf.upfronthosting.co.za>
In-reply-to
Content
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 (multiprocessing.tests.WithProcessesTestConnection) ...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa2e999f6e0 (LWP 10594)]
0x000000000052065f in PyCFunction_Call (func=Cannot access memory at
address 0x7ffeffffffd8
) at Objects/methodobject.c:73
73                              return (*meth)(self, arg);

Linux on AMD64 with Python 2.5 svn --with-pydebug.
History
Date User Action Args
2008-11-28 15:15:34christian.heimessetrecipients: + christian.heimes, gregory.p.smith, Rhamphoryncus, schmir, roudkerk, benjamin.peterson
2008-11-28 15:15:33christian.heimessetmessageid: <1227885333.71.0.671829505716.issue1683@psf.upfronthosting.co.za>
2008-11-28 15:15:33christian.heimeslinkissue1683 messages
2008-11-28 15:15:31christian.heimescreate