On Thu, 23 Jun 2005, Pedro Neves wrote:

> In the reply data that I show below, you can see that curl stopped and it
> seems to me that it stayed waiting for data since it has not reached the end
> of the reply. In this case, I had to make Ctrl-c to go back to gdb and
> perform backtrace (the curl crashed after receiving the character *n*).

It sounds like the server has told libcurl that there are N bytes coming, but
you only get N-X (where X is >= 1) and thus it sits waiting for the rest to
arrive. Does that seem possible to you?

Can you show us the HTTP response headers of one of these failures?

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