Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 14 Oct 2002 01:19:52 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin 1.3.13-2 idiosyncracy Message-ID: <20021014051952.GA16232@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i 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. >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 -- 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/