On Tue, 18 Sep 2007, junk_at_igrspace.com wrote:

PLEASE don't top-post. I write this in almost every reply these days. I might
soon switch over to NOT RESPOND AT ALL if everyone continues to violate the
netiquette of this list to this extent.

DO NOT TOP-POST! DO NOT FULL-QUOTE! (Sorry, this was not you personally who
made me burst, you just happened to be number #209 in the line doing the same
ignoring-of-the-rules.)

> indeed, the bad execution wasn't caused by this warning. I started debugging
> en found some strange behavior.

What about my question about helping out to fix the warnings?

> could it be my program executes too fast ? or is there an internal LIBSSH2
> timeout set too low ?

Can you make stand-alone libssh2 examples to run exactly as you want?

I mean, have you ruled out that this is a problem in libssh2, as if it is
you're better off fixing them first in the libssh2 camp.

If the ssh2-examples all work fine, we need to identify what makes libcurl's
use wrong in comparison to the working examples.

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