From: Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Report a Bug (#! bash bug)
Date: Sun, 09 Feb 2003 14:23:01 +1100
Organization: ECLiPSE
Lines: 16
Message-ID: <m1ib4v4ajsc7u98p3fuk3d8rhmjpnihddo@4ax.com>
References: <200302071836 DOT h17IamZQ092746 AT en26 DOT groggy DOT anc DOT acsalaska DOT net>
NNTP-Posting-Host: p24-max21.syd.ihug.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: lust.ihug.co.nz 1044760986 17680 203.173.153.216 (9 Feb 2003 03:23:06 GMT)
X-Complaints-To: abuse AT ihug DOT co DOT nz
NNTP-Posting-Date: Sun, 9 Feb 2003 03:23:06 +0000 (UTC)
X-Newsreader: Forte Agent 1.92/32.572
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>>    What version did you see this bug in? [2.03]

Have you tried Bash 2.04 or the 2.05b beta?

Bash 2.05bb is in beta testing at the moment and has not had any bug
reports against it that I am ware of or have seen. The source is
availabel from the following URL:
http://snowballville.tripod.com/djgpp/

A binary version can be found at the following URL:
http://clio.rice.edu/djgpp/win2k/main_204.htm

Please read the info on both of these pages very carefully and if you
get stuck send the authors an email.

Andrew