Mark Riordan wrote: > I think we are getting somewhere. > The upload fails after the test program outputs this: > libssh2_sftp_write 1 sent 32000 bytes; 32000 so far > libssh2_sftp_write 2 sent 500 bytes; 32500 so far > libssh2_sftp_write 3 sent 32000 bytes; 64500 so far > libssh2_sftp_write 4 sent 500 bytes; 65000 so far > > The trace log ends: .. > [libssh2] 0.724547 SFTP: Received packet 101 (len 24) > [libssh2] 0.724547 SFTP: Asking for 101 packet > [libssh2] 0.724547 SFTP: Got 101 > [libssh2] 0.740171 Conn: Writing 4029 bytes on channel 0/0, stream #0 > [libssh2] 0.740171 Conn: Sending 4029 bytes on channel 0/0, stream_id=0 > [libssh2] 0.740171 Socket: Sent 4292/4292 bytes at 00994194 > [libssh2] 0.740171 Conn: Writing 4029 bytes on channel 0/0, stream #0 > [libssh2] 0.740171 Conn: Sending 4029 bytes on channel 0/0, stream_id=0 > [libssh2] 0.740171 Socket: Sent 4292/4292 bytes at 00994194 > [libssh2] 0.740171 Conn: Writing 4029 bytes on channel 0/0, stream #0 > [libssh2] 0.740171 Conn: Sending 4029 bytes on channel 0/0, stream_id=0 > [libssh2] 0.740171 Socket: Error sending 4292 bytes: 11
That's WSAEWOULDBLOCK or EAGAIN.. > I put the full trace here: > http://trac.libssh2.org/attachment/ticket/197/2010-11-12b-error-11.zip > but I doubt you'll need it. Let's see.. //Peter _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
