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: eos.vss.fsi.com: ford owned process doing -bs
Date: Wed, 3 Dec 2003 10:35:53 -0600 (CST)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
Subject: Re: Bash wait indefinitely
In-Reply-To: <20031202173201.GD13980@redhat.com>
Message-ID: <Pine.GSO.4.58.0312031017160.28297@eos>
References: <20031202173201 DOT GD13980 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 2 Dec 2003, Christopher Faylor wrote:
> On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
> >Thomas Pfaff's 2003-12-01 pthread change might have fixed it.
> >
> I don't see why it would.  bash doesn't use pthreads, AFAIK.
>
Sorry, I still need to learn not to say stupid speculative things without
thinking them through first :D.

> >Could you try a snapshot that includes it?
> >
FWIW, I ran the test case overnight on my old 450 MHz Pentium Pro SGI 320
running NT4, all packages up-to-date, and a cvs compiled cygwin1.dll from
2003-11-25 without issue.  When my dual CPU system gets back, I'll try it
there.

Even though we don't expect that this is fixed, could those that can
reproduce this problem try it with a snapshot?  Since 1.5.6 is near, it
would be good to check it now.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

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