Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 16 Aug 2005 21:55:58 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: openssh-4.1p1-2/cygwin-1.5.18-1: write(2) misbehaving?
Message-ID: <20050816195558.GA13979@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CB0EAF8A515FC4488F2B4B546BEE012CA0EB07@islexch2k.isllcnets.studentloan.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB0EAF8A515FC4488F2B4B546BEE012CA0EB07@islexch2k.isllcnets.studentloan.org>
User-Agent: Mutt/1.4.2i

On Aug 16 14:33, Dave Kilzer wrote:
> On Tuesday, August 16, 2005 4:33 AM, Corinna Vinschen wrote:
> > So, first step, could you please try the latest snapshot DLL from
> > http://cygwin.com/snapshots/ and see if the problem persists?  If so,
> > we will have to do some debugging together.
> 
> I tried the 2005-Aug-14 snapshot (by exiting out of all Cygwin windows,
> renaming /bin/cygwin1.dll to cygwin1.dll.orig, and copying in the
> unarchived snapshot renamed to cygwin1.dll; verified with cygcheck after
> opening a new Cygwin window), and it had the same problem.  I also tried
> the 2005-Jul-28 snapshot (which was ~9 MB unpacked), and it still had
> the same problem as well.

Ok, I have attached another Cygwin DLL for your consumption.  If the cause
of this problem is what I suspect, this DLL should solve your problem,

BUT

it will print annoying messages to the console, containing a text as
"res and ret = 0, nonblocking = 1".

I'll send the URL of the DLL in private mail in a minute.

> Are there older snapshots or revisions between 1.5.13 and 1.5.18 that I
> can try?  I could use a binary search algorithm to narrow down which
> snapshot or release first saw the problem.

Not officially.  This isn't quite the way we should go.  I'd rather
catch the problem in the current sources.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

