On Wed, 16 Sep 2009, richard oehlinger [celum] wrote:
Ok, I've following calling stack:
Please don't top-post or full-quote.
Curl_socket_ready(unsigned int readfd=0x00000124, unsigned int
writefd=0xffffffff, int timeout_ms=0x00000000) Zeile 287
as you can see the writefd was - I assume correctly - set to
CURL_SOCKET_BAD, but curl does keep on running (all the way up to the
Transfer method) and the call of "select" always returns 0 (== timeout).
That quite clearly looks wrong, I agree. The problem here is of course to
figure out how it got to be that wrong in the first place. The source of the
problem rather than the sympthom I mean.
Is there any way to check if a specific fd is still up?
A specific fd is just a descriptor for a socket, and that socket may be
representing a TCP connection and that TCP connection may of course still be
"up" and there are a few basic checks one can do but none are guaranteed
success. And I don't see how that would help in this particular case anyway.
--
/ daniel.haxx.se
