[issue3311] block operation on closed socket/pipe for multiprocessing

Changes by STINNER Victor : -- resolution: -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue3311] block operation on closed socket/pipe for multiprocessing

STINNER Victor added the comment: This issue was fixed by r68768 for issue #3321. -- status: open -> closed ___ Python tracker ___ ___

[issue3311] block operation on closed socket/pipe for multiprocessing

STINNER Victor added the comment: ping? The bug is still open and valid. -- versions: +Python 2.7, Python 3.0, Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue3311] block operation on closed socket/pipe for multiprocessing

STINNER Victor added the comment: This issue is not critical anymore because jesse.noller fixed the crash in r68768. Python 2.7a0 (trunk:68873M, Jan 23 2009, 08:46:25) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more

[issue3311] block operation on closed socket/pipe for multiprocessing

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- keywords: +needs review priority: -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3311] block operation on closed socket/pipe for multiprocessing

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- assignee: -> jnoller nosy: +jnoller, roudkerk ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3311] block operation on closed socket/pipe for multiprocessing

New submission from STINNER Victor <[EMAIL PROTECTED]>: _multiprocessing Connection methods don't check if handle is valid or not. If you close the socket/pipe, Python may crash on operations, especially in poll() on FD_SET(...handle, &rdfs). Example of crash: -- import _mu