On Wed, 20 Aug 2003, Antoine Calando wrote:

> < HTTP/1.1 100 Continue
> Segmentation fault

[snip]

> Any idea?

Thanks for an excellent report. I could repeat the problem at once, and I
think the attached patch corrects the problem the proper way. At least it made
the example code do good at my place.

Let us know if it doesn't cure your decease.

> CURLMsg * curl_multi_info_read( CURLM *multi_handle, int *msgs_in_queue);
>
> If the function returns a NULL pointer, msgs_in_queue is not set to 0. It
> can be confusing if this variable was initialised with a value different
> from 0.

Oops. I've fixed this too now.

Thanks for your report!

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998

-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104