[ruby-core:60867] [ruby-trunk - Bug #9356] TCPSocket.new does not seem to handle INTR

Issue #9356 has been updated by Eric Wong.


 Eric Wong <[e-mail]> wrote:
 > Ah, I forget the outer for(;;) loop.  Maybe it's better to not loop,
 > the WAIT_IN_PROGRESS stuff is confusing...
 
 I have no idea how portable this is:
 	http://bogomips.org/ruby.git/patch?id=f5e2eb00e5
 
 Btw, I suspect the WAIT_IN_PROGRESS stuff is carried over from the
 1.8 days where all sockets were non-blocking by default, and overly
 complicated as a result.  I don't even think EINPROGRESS/EAGAIN is
 possible, only EINTR/ERESTART.

----------------------------------------
Bug #9356: TCPSocket.new does not seem to handle INTR
https://bugs.ruby-lang.org/issues/9356#change-45278

* Author: Charlie Somerville
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: -
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
TCPSocket.new does not seem to handle EINTR properly.

In the attached test script, I try to open a TCP connection to my server and make an HTTP request while a background thread continually sends a signal to the process.

This causes the #write call to fail with:

x.rb:13:in `write': Socket is not connected (Errno::ENOTCONN)
	from x.rb:13:in `<main>'

This also appears to affect 2.0.0. 1.9.3 is unaffected.

---Files--------------------------------
socket-eintr.rb (207 Bytes)


-- 
http://bugs.ruby-lang.org/