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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Mon, 14 Oct 2002 09:58:43 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.3.13-2 idiosyncrasy
In-Reply-To:	<20021014051952.GA16232@redhat.com>
Message-ID:	<Pine.GSO.4.44.0210140951560.3007-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Mon, 14 Oct 2002, Christopher Faylor wrote:

> On Mon, Oct 14, 2002 at 01:11:44AM -0400, Igor Pechtchanski wrote:
> >Hi,
> >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 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.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51


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