Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Tue, 4 Mar 2003 22:54:01 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Cc: h DOT m DOT brand AT hccnet DOT nl
Subject: Re: cygwin snap 20030223 hangs with bleadperl
Message-ID: <20030305035401.GB2524@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, h DOT m DOT brand AT hccnet DOT nl
References: <20030304095413 DOT 1E4B DOT H DOT M DOT BRAND AT hccnet DOT nl> <Pine DOT GSO DOT 4 DOT 44 DOT 0303041022051 DOT 25599-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.44.0303041022051.25599-100000@slinky.cs.nyu.edu>
User-Agent: Mutt/1.5.1i

On Tue, Mar 04, 2003 at 10:23:14AM -0500, Igor Pechtchanski wrote:
>On Tue, 4 Mar 2003, H.Merijn Brand wrote:
>
>> On Tue 04 Mar 2003 06:01, Christopher Faylor <cgf-cygwin AT cygwin DOT com> wrote:
>> > On Wed, Feb 26, 2003 AT 03:20:02PM +0100, H.Merijn Brand wrote:
>> > >On Tue 25 Feb 2003 14:15, "H.Merijn Brand" <h DOT m DOT brand AT hccnet DOT nl> wrote:
>> > >> ../ext/IO/lib/IO/t/io_udp..............ok
>> > >> ../ext/IO/lib/IO/t/io_unix.............ok 1/5
>> > >>
>> > >> 20030220 still OK
>> > >
>> > >20030225 also hangs
>> > >
>> > >(Note that I'm still not on the list)
>> >
>> > Is it better now?
>> >
>> > cgf
>>
>> Yep.
>>
>> CYGWIN_NT-5.0 PC09 1.3.21s(0.77/3/2) 20030302 23:00:55 i686 unknown unknown Cygwin
>>
>> Completed the smoke. I was discussing a longstanding Cygwin issue yesterday
>> with some other smokers and we all agreed that there is still a glitch in
>> cygwin that /we/ think cygwin is to blame for.
>>
>> Running the complete test from the prompt completes without error, but when
>> started from a script in the background, there are still messages that get a
>> <CR> added and unexpectedly yield <CR><NL> instead of plain <NL>, causing
>> these tests to fail: Expected Foo<NL>, got Foo<CR><NL>
>>
>> $CYGWIN is "tty ntsec binary"
>                        ^^^^^^
>Umm, there is no such setting in the CYGWIN environment variable.  Perhaps
>you meant to say "binmode"?
><http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>

Shouldn't matter binmode is the default.  I suspect that there is a non-cygwin
application lurking in the mix somewhere?

If it's a perl script, then maybe something is explcitly setting binmode(0).

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/