Message-Id: <3.0.16.19980213135156.3577667c@hem1.passagen.se>
Date: Fri, 13 Feb 1998 15:15:35 -0500
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
From: Peter Palotas <blizzar AT hem1 DOT passagen DOT se>
Subject: Re: Bash crashing!
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

At 13.43 1998-02-13 +0100, you wrote:
>In article <3 DOT 0 DOT 16 DOT 19980212200915 DOT 358fdc8c AT hem1 DOT passagen DOT se> you wrote:
>[...]
>> Hehehe... Yeah, guess I didn't do that. BUT... I discovered something...
>> You told me to insert set -x at the beginning, and I did so, and it didn't
>> crash! Then I removed set -x, and it crashed, then I inserted a blank line
>> before the first comment (#!/bin/sh), and it worked again.
>
>Aha! Looks like whatever '/bin/sh' it finds on your machine, is the
>cause of these errors, then. Please be sure that all 'sh' and 'sh.exe'
>files on your machine are really (the current release of) bash, and
>nothing else.

Yes, ofcourse that's the reason! ;)  I was certain that I had the current
bash.exe as sh.exe in /bin, but I really had it in /usr/bin/sh.exe ...
Argh! But anyway, *SHOULD* bash crash because of this?


-- Peter Palotas alias Blizzar -- blizzar AT hem1 DOT passagen DOT se --

******************************************************
* A brief description of DJGPP:                      *
* NEVER BEFORE HAVE SO FEW DONE SO MUCH FOR SO MANY! *
******************************************************