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
IO::Handle::blocking seems to break the socket entity under windows 7
64bit(possible other OS'es).
Attached is an example of breaking code: please adjust the port and
address to something that is open on your side, and then try
uncommenting either of the IO::Handle::blocking calls. The connect will
fail with "unknown error" or "A non-blocking socket operation could not
be completed immediately." depending on the perl distribution.
Please note that $sock->blocking(0) or $sock->blocking(1) will also fail
the same way.
Issue present in both activeperl 5.10.1 and strawberry perl 5.12.1.
This was originally fixed in 375ed12 but then broken again in 375ed12, and the branch (which is in CI on my tonycoz/perl5 fork) fixes that.
The original report is a little confusing in that if you switch blocking off for a socket the connect() should fail with "A non-blocking socket operation could not be completed immediately."
Migrated from rt.cpan.org#61074 (status was 'new')
Requestors:
Attachments:
From deathwolf+bitcard@gmail.com on 2010-09-05 02:12:17:
From deathwolf+bitcard@gmail.com on 2010-09-05 11:39:54:
Additional bug reference for a similar bug that might be related #17448
The text was updated successfully, but these errors were encountered: