[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

Changes by Charles-François Natali : -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

Kristian Vlaardingerbroek added the comment: On Python 2.7.2 this can not be reproduced. Instead of the segmentation fault an AssertionError is raised: AssertionError: invalid Element proxy at 39359432 In Python 3.2 the p1.send(n) step in the example raises a PicklingError when trying to pa

[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

Ask Solem added the comment: Can't reproduce on Python 2.7, but can indeed reproduce on 2.6. Issue fixed? -- ___ Python tracker ___ _

[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

Changes by Brian Curtin : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

Changes by Benjamin Peterson : -- assignee: -> jnoller nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue9955] multiprocessing.Pipe segmentation fault when recv of unpicklable object

New submission from Zbynek Winkler : $ python Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> from pickle import dumps >>> from multiprocessing import Pipe >>> n = etree.E