Daniel Stenberg wrote:
> 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.

Actually, it doesn't work... but it is strange because I remember I applied the patch
and it seemed that it was working correctly, but it doesn't work anymore now!!!
(May be I didn't do the right tests?)

My last tries were with versions 7.10.6 and .7, and with/without multi-segfault.patch
The only difference with the preceding report is that we don't have the line
"< HTTP/1.1 100 Continue" printed just before the segfault :
----------------------------------------------------------------------------------------------
antoine_at_tech04 ~/src/curl-7.10.7/docs/examples> multi-post localhost/cgi-bin/test
* About to connect() to localhost:80
* Connected to localhost (127.0.0.1) port 80
> POST /cgi-bin/test HTTP/1.1
Host: localhost
Pragma: no-cache
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Content-Length: 3301
Expect: 100-continue
Content-Type: multipart/form-data; boundary=curl4ji60t7BoaA9rd17NkmWggOUCqa

Segmentation fault
-----------------------------------------------------------------------------------------------

But this answer, even if it is not printed, is received (I checked the tcp stream).

Anyway, thanks for your work!

Antoine

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-08-29