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 (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. ---------- resolution: fixed -> status: closed -> open versions: +Python 2.5.3 _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1683> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
