After adding debugging code as you advised, I did observe that handles got
stuck in the state of CURLM_STATE_WAITRESOLVE. I guess there's a bug in
the Curl_is_resolved() or host_callback(), although I can't figure it out
now.

> On Mon, 29 Mar 2004, Roy Shan wrote:
>
>> > Can you make some kind of debug output to see if the stuck handles are
>> in
>> > this state when they stall?
>>
>> How to check the handle internal state? The getinfo function doesn't
>> have an
>> option for that.
>
> No, you would need to edit lib/multi.c and see how the #ifdef CURLDEBUG is
> made in the beginning of the curl_multi_perform() function and see if you
> can
> make something similar. The multi handle keeps a state for each single
> easy
> handle, but it is strictly internal.
>
> --
> Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> Dedicated custom curl help for hire: http://haxx.se/curl.html
>
Received on 2004-03-30