On Tue, 4 May 2010, Xu, Qiang (FXSGSC) wrote:

> Coz I've had no luck with "libssh2_trace(sshc->sftp_session, ~0)" so far,
> some other method has been tried:

What do you mean "no luck" with that? Surely it produced some kind of output?
If not, did you really build libssh2 with debug tracing enabled?

> /* log for transfer failure */
> qxu@durian(pts/1):~/opensrc/curl-7.20.1/src[254]$ ./curl -v -k -u <user>:<pass> -T testSmall.pdf sftp://13.121.8.133/Home/Scans/

> 3 511k 0 0 3 16311 0 1422 0:06:08 0:00:11 0:05:57 1492 3 511k 0 0 3 16311 0 1307 0:06:40 0:00:12 0:06:28 1367*
> libssh2_sftp_write() writes [-7] bytes
> } [data not shown]
> * libssh2_sftp_write() writes [-7] bytes
> } [data not shown]
> * libssh2_sftp_write() writes [-7] bytes

> How come libssh2_sftp_write() returns -7 rather than -37
> (LIBSSH2_ERROR_EAGAIN)? From libssh2.h, it can be seen -7 is
> LIBSSH2_ERROR_SOCKET_SEND. Is it suggesting the response from the server is
> not what we expected?

That's what we need to figure out, and that's where the libssh2_trace() might
help to fill in some blanks.

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