From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>, "Mark E." <snowball3 AT bigfoot DOT com>
Cc:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Subject:	Re: Possible bash issue
Date:	Mon, 21 May 2001 17:59:29 +0200
Message-ID:	<CAEGKOHJKAAFPKOCLHDIEEHFCDAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to:	<2950-Mon21May2001063028+0300-eliz@is.elta.co.il>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Importance:	Normal
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > 
> > At 16, it means the script thinks the max length is 147457.
> 
> So it still is larger than the transfer buffer, and thus the results
> of the test are wrong.
> 
OK - so we need an exception for DJGPP, say 16K as default?
What test would you suggest to detect DJGPP from the shell?
Is
  test -r /dev/env/DJDIR/djgpp.env
enough?  Then again, ltconfig gets the host anyway, so we could just
use that.

BTW, the 'official' bash binary still has the crash problem with this
test, so it is most likely a WinME problem.  OTOH, it seems to always
be a segmentation fault in free(), which would suggest some memory is
freed twice.  If I have the time, I'll try to build bash with mss or
dmalloc (depending on how easy it is to add such testing).

- Raw text -