You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2010-01-10.00:41:41.395>created_at=<Date2008-07-07.01:18:40.160>labels= ['library']
title='block operation on closed socket/pipe for multiprocessing'updated_at=<Date2010-01-10.00:41:51.265>user='https://github.com/vstinner'
_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).
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 information.
>>> import _multiprocessing
>>> obj = _multiprocessing.Connection(755)
>>> obj.close()
>>> obj.poll()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
IOError: handle out of range in select()
I would prefer a message "I/O operation on closed socket", but you can
close this issue.
Note: I proposed a similar patch to improve the error message ("I/O
operation on closed socket") for the socket module in issue bpo-4853.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: