Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Subject:	Re: maintaining bash
MIME-Version:	1.0
Date:	Fri, 8 Apr 2005 14:56:31 +0200
Message-ID:	<79F81D5F4790D344B05F489CE2AC8AB717CEFA@dubexdc03.dubex.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"David Dindorp" <ddi AT dubex DOT dk>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j38Cunfb019564

Brian Dessent wrote:
> David Dindorp wrote:
>> Uhm.  No it's not..
>> Bash 2.05b is so unstable under Cygwin that it classifies as a
>> volatile chemical.  At least if you put it under a lot of pressure -
>> a normal users everyday use it may cope fine with, which is probably
>> how it's used by most people in here anyway.
>> 
>> To be fair, this is probably more a Cygwin DLL problem than a bash
>> problem, or perhaps a "bash hasn't kept up with changes in Cygwin
>> because the maintainer haven't had the time" problem.  It's running
>> quite stable under 1.5.10, it sucks with 1.5.12 and 1.5.13 and any
>> of the latest snapshots..  (Haven't tried 1.5.11, but I will as soon
>> as I get the time.)
> 
> I would say it's probably got to do more with changes in the cygwin
DLL
> than bash.  There's the PID reuse issue that has a workaround in the
-17
> package by Pierre's patch, and the // thing that Corinna mentioned.

Just for reference, I'm also referring to -17.

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

- Raw text -