On Thu, 2 Nov 2006, James Buchanan wrote:

>> The dump looks fine all the way to line 185 where there's something _after_
>> the final chunk.

BTW, the line 185 was from when loading your trace into emacs.

> It works now with the latest curl version. There's a problem with
> curl_easy_free() though on my system; memcmp() in /lib/tls/libc.so.6
> segfaults. Obviously not a curl issue. I'll take it up with the Debian TLS
> package maintainers perhaps.

Well, you could still make a stack trace for us and show, and we might be able
to spot something.

> There is another issue. curl_easy_perform() returns an error "couldn't send
> data to peer" even though immediately after that I get the error string and
> the HTTP return code is 200.

I don't get it. How do you get the error string and HTTP return code? What's
the exact return code you get from curl_easy_perform() ?

> It works, but perhaps it tries a few times, sets the error, then it works
> and hence the bad return code but it's actually worked after a few tries?

libcurl never "tries a few times" on its own.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html