Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <3.0.5.32.20041119001406.0081bab0@incoming.verizon.net>
X-Sender: vze1u1tg AT incoming DOT verizon DOT net
Date: Fri, 19 Nov 2004 00:14:06 -0500
To: cygwin AT cygwin DOT com
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject: Re: scp exits often with -1
In-Reply-To: <cniv16$534$2@sea.gmane.org>
References: <20041118155449 DOT GG10795 AT trixie DOT casa DOT cgf DOT cx> <20041118172729 DOT D51B6E523 AT wildcard DOT curl DOT com> <20041118185309 DOT GA246157 AT Worldnet>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id iAJ5Jqhc015466

At 09:00 PM 11/18/2004 +0100, Jörg Schaible wrote:
>Pierre A. Humblet wrote:
>> 
>> 109 is "The pipe has been ended". Isn't that strange when reading a pipe?
>> Unfortunately fd 4 was opened in a part of the trace that we don't have.
>
>I'll have a look tomorrow in the office, where fd 4 came from (thought I
>posted all related stuff, but trace is hard). Still have the full protocol
>though.

I had a second look at this. It's easy to correlate the trace with the
-v outputs you provided in
http://cygwin.com/ml/cygwin/2004-11/msg00637.html   
The debug outputs correspond to lines such as "N = write (2, xxx)",
where N is the length of the debug line.

For example
   36  676149 [main] ssh 4392 writev: writev (2, 0x22A400, 1)
   34  676183 [main] ssh 4392 fhandler_base::write: binary write
   45  676228 [main] ssh 4392 fhandler_base::write: 40 = write (0x22A830, 40)
   34  676262 [main] ssh 4392 writev: 40 = write (2, 0x22A400, 1), errno 119
 debug2: channel 0: read<=0 rfd 4 len 0   <= THIS IS THE DEBUG OUTPUT
   36  676298 [main] ssh 4392 __cygwin_lock_lock: threadcount 1.  not locking

Once you know that, it's easier to follow what's going on. It would be
interesting to compare traces of successful and failed runs, in the area
where their debug outputs differ.

Pierre

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/