On Sat, 7 Feb 2009, Markus Moeller wrote:
(I removed curl-users as a receiver as this is plain libssh2 talk)
> I think this would fix libssh2
>
> --- src/channel.c 2009-02-06 23:57:47.0 +
> +++ src/channel_new.c 2009-02-06 23:57:42.0 +
> @@ -1771,6 +1771,7 @@
>
I think I now know under which rare circumstances this happens and it is a
bug in libssh2.
I can simulate it with (e.g. a packet is not completly written and the
attempt to write the rest creates EAGAIN):
In below simulation the 10 packet is reduced by 30 bytes and the attempt to
write the 30
"Markus Moeller" wrote in
message news:gmi9el$hi...@ger.gmane.org...
>I did some more debug. Here are my questions:
>
> Normal:
> Curl_write calls Curl_scp_send
>
> MMM Curl_scp_send after libssh2_channel_write len/nwrite 16384/16384
> MMM Curl_write after Curl_scp_send len/nwrite 16384
I did some more debug. Here are my questions:
Normal:
Curl_write calls Curl_scp_send
MMM Curl_scp_send after libssh2_channel_write len/nwrite 16384/16384
MMM Curl_write after Curl_scp_send len/nwrite 16384/16384
MMM Curl_scp_send after libssh2_channel_write len/nwrite 16384/16384
MMM
"Daniel Stenberg" wrote in message
news:alpine.deb.1.10.0902040905110.27...@yvahk2.pbagnpgbe.fr...
> On Tue, 3 Feb 2009, Markus Moeller wrote:
>
>>> [libssh2] Connection: Sending 39 bytes on channel 0/0, stream_id=0
>>> [libssh2] Connection: libssh2_packet_write returned EAGAIN
>>> 100 112k
On Tue, 3 Feb 2009, Markus Moeller wrote:
>> [libssh2] Connection: Sending 39 bytes on channel 0/0, stream_id=0
>> [libssh2] Connection: libssh2_packet_write returned EAGAIN
>> 100 112k0 00 112k 0 95334 --:--:-- 0:00:01 --:--:--
>> 219k[l
>> ibssh2] Connection: Sending 16345
