Date: Wed, 12 Jan 2000 08:51:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: jazir <entropic AT mpx DOT com DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: upgrade chaos
In-Reply-To: <387B38E0.1047EF30@mpx.com.au>
Message-ID: <Pine.SUN.3.91.1000112085053.28074F@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Jan 2000, jazir wrote:

>   cuz now i have no idea which change caused my problems.  i have a textfile
> {de}/compression program that i wrote, and it used to work fantastically with
> all kinds of files, even very large ones.
> 
>   when compiled with my new installation, i get SIGSEGV in the function free()

What was the previous version of DJGPP you had installed?  If it was
v2.01 (not v2.02), then what you see is a bug in your program that
simply went unnoticed before v2.02.  Version 2.02 introduced a new,
more space-efficient version of malloc/free, which is now much less
tolerant to programs that write beyond the end of an allocated buffer,
or free a buffer more than once.

Try using some malloc debugger, like YAMD, to hunt down that bug.