From: Mark Elliott <elliott AT uni-leipzig DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: upgrade chaos
Date: Wed, 12 Jan 2000 10:42:00 +0100
Organization: Uni Leipzig
Lines: 37
Message-ID: <387C4C68.2B736BA4@uni-leipzig.de>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000112085053 DOT 28074F AT is>
NNTP-Posting-Host: pmi9.isdn.uni-leipzig.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: news.uni-leipzig.de 947670303 13649 139.18.110.74 (12 Jan 2000 09:45:03 GMT)
X-Complaints-To: usenet AT news DOT uni-leipzig DOT de
NNTP-Posting-Date: 12 Jan 2000 09:45:03 GMT
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en,sr,de-DE
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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

To clarify, I upgraded from v2.01, and am using code originally written for Borland
C, in which it is sometimes necessary to free some more memory than was originally
allocated (i.e. free(var+4);). Given that I kept this style, the explanation above
probably accounts for my problems, thanks a lot for pointing this out ( - in
advance, I haven't tested my code without the modification yet).

Mark

--
-----------------------------------

Mark A. Elliott

Universität Leipzig.
Institut für Allgemeine Psychologie.
Seeburgstr. 14/20,
D-04103 Leipzig.
Germany

Tel: ++49 (0)341 97 359 57
Fax: ++49 (0)341 97 359 69

email: elliott AT uni-leipzig DOT de

-----------------------------------