From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	<djgpp-workers AT delorie DOT com>, "Mark E." <snowball3 AT bigfoot DOT com>
Date:	Mon, 21 May 2001 14:38:06 -0400
MIME-Version:	1.0
Subject:	Re: Possible bash issue
Message-ID:	<3B09284E.18362.9B52E@localhost>
In-reply-to:	<CAEGKOHJKAAFPKOCLHDIEEHFCDAA.tim.van.holder@pandora.be>
References:	<2950-Mon21May2001063028+0300-eliz AT is DOT elta DOT co DOT il>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
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

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

You can build with --with-bash-malloc. Bash's malloc will detect when memory 
has been freed twice and abort.

I think free() should abort (or something similiar) if the block it's been 
asked to free has already been freed. This would allow the error to detected 
at the source of the problem instead of sometime later when the program 
finally crashes.

Later,
Mark

- Raw text -