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:	Mon, 14 Oct 2002 11:11:59 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.3.13-2 idiosyncrasy
Message-ID:	<20021014151159.GB20349@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20021014051952 DOT GA16232 AT redhat DOT com> <Pine DOT GSO DOT 4 DOT 44 DOT 0210140951560 DOT 3007-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version:	1.0
In-Reply-To:	<Pine.GSO.4.44.0210140951560.3007-100000@slinky.cs.nyu.edu>
User-Agent:	Mutt/1.4i

On Mon, Oct 14, 2002 at 09:58:43AM -0400, Igor Pechtchanski wrote:
>On Mon, 14 Oct 2002, Christopher Faylor wrote:
>> On Mon, Oct 14, 2002 at 01:11:44AM -0400, Igor Pechtchanski wrote:
>> >I'm not sure if this is a bug, or just weird behavior, but on the new
>> >Cygwin the output of 'ps' shows all bash shells but the current one in the
>> >'waiting for tty input' state (an 'I' in the first column).
>>
>> What's wrong with that?  The current one is not waiting for input if it
>> is running ps.
>
>Well, there's nothing wrong with it per se, which is why I labeled it an
>idiosyncrasy (sorry for the original spelling), and not a bug.  However,
>this is not the behavior it used to have before, and other Unixes don't
>have it either...  But if this is the way it should be, then fine, I can
>live with that...

I just checked and it is like this in 1.3.12, too.  It is working as I
would expect it to work.

>> >I also got a bash into a 'stopped' state (an 'S' in the first column of ps
>> >output) by minimizing an xterm quickly, while bash is loading.  This is
>> >only possible to reproduce when cygwin1.dll is not yet loaded, so bash
>> >waits for it.  Sounds like some sort of a race condition...  I'm not sure
>> >how to debug this or provide any additional info.
>>
>> And I don't understand.  How can you get xterm started without having
>> cygwin1.dll loaded?
>> cgf
>
>Oops, sorry, you're right, of course...  What I meant was that the only
>way I could reproduce this was to unload all cygwin programs, and then
>start a few xterms in quick succession and minimize them all.  Then some
>bash shells would stay in a "stopped" state.  They may be waiting for some
>other dll, for all I know, but as soon as even one bash is loaded, other
>bash sessions initialize much too quickly for me to minimize the xterm and
>reproduce the problem.

I don't see how waiting for a DLL would force something into a suspended
state.

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

- Raw text -