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: Tue, 2 Dec 2003 12:32:01 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Bash wait indefinitely Message-ID: <20031202173201.GD13980@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3FC7AC79.2010000@myrealbox.com> <20031129221554.GA26957@ally.rlsystems> <3FCBA38F.9050902@m4x.org> <20031202121452.GA9651@linux_rln.harvest> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote: >On Tue, 2 Dec 2003, Ronald Landheer-Cieslak wrote: >> On Mon, Dec 01, 2003 at 12:24:47PM -0800, Antoine Labour wrote: >> > Ronald Landheer-Cieslak wrote: >> > >Unfortunately, I don't have any system with more than one CPU, so there's >> > >no way I can test it on a system like that and I have not run into any >> > >similar problems on any of the systems I have.. (Cygwin or otherwise). >> > > >I do, and have. In fact, the problem seemed worse in more recent Cygwin >snapshots. Although, I have not tested this scenerio in a week or two >now. And, Thomas Pfaff's 2003-12-01 pthread change might have fixed it. >Could you try a snapshot that includes it? I don't see why it would. bash doesn't use pthreads, AFAIK. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/