Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 9 Nov 2000 12:54:28 -0500 From: Christopher Faylor To: cygwin@sources.redhat.com Subject: Re: [ANNOUNCEMENT] cygwin-1.1.5-6, mingw-20001103-1, w32api-20001103-1, gcc-2.95-4 Message-ID: <20001109125428.L1629@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20001108213347.A3298@redhat.com> <3A0ADA6C.D1F2A3B6@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <3A0ADA6C.D1F2A3B6@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Nov 09, 2000 at 12:10:04PM -0500 On Thu, Nov 09, 2000 at 12:10:04PM -0500, Charles S. Wilson wrote: >I seem to remember this being report earlier, but I couldn't find it -- >besides, it was related to an older 1.1.5-x. I had hoped this error had >been fixed, but apparently not since I just saw it again with >cygwin-1.1.5-6: > >Sometimes when starting a cygwin app from within bash, the bash prompt >will return immediately but ps shows that the app (say, vim) is still >running in the 'S' state. However, it's not in the background -- there >does not seem to be anyway to 'foreground' that application. All I can >do is kill it, and try again. > >This happens *very* infrequently, so it's extremely hard to track down >-- in fact, it had been so long since I had seen the error, and mindful >that I think it had already been reported, I assumed it had been fixed. >But it hasn't. I can't duplicate this. It will be in the release version. Have fun. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com