[Multi] "select(): Bad file descriptor" on a terminated socket about curb HOT 3 CLOSED

From a bit of googling around, it looks like defining a CURLMOPT_SOCKETFUNCTION callback might be required to handle this (the documentation is unclear, and the socket function proper is deprecated)

For the record, I'm running curl 7.19.5

Update: and now I'm not so sure - that seems to be valid for when you're manually telling curl to process a socket (libevent and whatnot), but not for the standard select() paradigm?

from curb.

Hey nevir,

I think it might be a race condition in the threading code around Curl::Multi, that's causing the errors... I created this reduced test case here: http://github.com/taf2/curb/blob/ab433db38df1e86cfc0261796a96fe1cb3cde209/tests/tc_curl_multi.rb#L324


I believe that tests the condition you described.


You are correct when using standard select defining a CURLMOPT_SOCKETFUNCTION is not required. evdispatch, is a libcurl library that tries to implement what I believe you want in C with a libev loop. http://evdispatch.rubyforge.org/ (although, i can't say it's stable...)


Looking at the requester.rb code, I think there is potentially a race condition causing the Bad file descriptor errors...

from curb.

I believe the issue as described is covered in the test above, can reopen if you disagree.

from curb.