Date: Mon, 11 Aug 1997 13:18:25 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: BASH Problems
In-Reply-To: <199708102002.AA168073362@typhoon.rose.hp.com>
Message-ID: <Pine.SUN.3.91.970811131805.7085C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 10 Aug 1997, Andrew Crabtree wrote:

> > Does the version on SimTel work in a stable manner?  If not, please
> > tell more about your system configuration.
> 
> No.  Originally (maybe 5 months ago), I tried using that (simtel v.)
> and had the same problems.  That's what prompted me to bootstrap
> from unix when building gcc.  I also just recently tried the bash 2
> alpha and that also had the same trouble.  My systems is fairly
> plain I believe.  Pentium, Windows 95, UniVBE loaded, LFN=y.
> Nothing else of interest.

Something is clearly wrong with your setup, so please try to
understand what that is.  The version on SimTel.NET works flawlessly
for me, both interactively and as a batch shell to run configure
scripts.  I have used that version to run extremely complex scripts
(to configure packages such as TeX) without any problems.

I use Bash on DOS (no Windows), but Daisuke Aoyama, the author of the
DJGPP port, works on Windows 95 and I don't imagine he would release a
port which cannot work for more than a few minutes.

Maybe your Bash startup files specify something that triggers the
bug.  Please try running without any _bashrc etc.

If that doesn't help, please try to tell more about your system
specifics, like the environment variables.  Unloading UniVBE is worth
trying (that's just a wild guess, but it's a good idea to get it out
of your way).

In any case, sending the crash traceback to Daisuke Aoyama might
help.