> If I had known the answer I wouldn't have asked you. You should debug this 
> case. Single-step into libcurl and see what internal call makes it return a 
> failed init. It is a rather early fail and there's not a lot of places that 
> _can_ reeturn that code so it shouldn't be that deep or strange.


I set the CURLOPT_VERBOSE 1  and run test code.
It says "Failure establishing ssh session". I find it in ssh.c .It call the 
libssh2_session_startup() and return a value .


> I suspect a third party library failure somehow.


Maybe you are right. The libssh2's libssh2_session_handshake(x,y) cause the 
code 2.


How to fix it ? Can you give me some advice?Thank you 


------------------ Original ------------------
From:  "daniel";<[email protected]>;
Date:  Thu, Feb 20, 2014 10:47 PM
To:  "libcurl development"<[email protected]>; 

Subject:  Re: sftp multi thread init question



On Thu, 20 Feb 2014, ?????? wrote:

> now it on the list !!!

Yes, and now you only need to start learning how not to top-post: 
http://curl.haxx.se/mail/etiquette.html#Do_Not_Top_Post

> I do not know what makes it return 2 . The error code say init failed . 
> There is a little information about the code <2>.But what makes it,can you 
> tell me? Is the test code wrong?  why does it init 10 threads successfully 
> every time ?

If I had known the answer I wouldn't have asked you. You should debug this 
case. Single-step into libcurl and see what internal call makes it return a 
failed init. It is a rather early fail and there's not a lot of places that 
_can_ reeturn that code so it shouldn't be that deep or strange.

I suspect a third party library failure somehow.

-- 

  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html
.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to