Date:	Thu, 28 Dec 2000 06:42:56 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Alex Oleynikov <alex AT compuweigh DOT com>
cc:	DJGPP Mail List <djgpp AT delorie DOT com>
Subject:	Re: libc _free exception
In-Reply-To:	<NEBBKABEDKFPFBKEMBFOAELOCAAA.alex@compuweigh.com>
Message-ID:	<Pine.SUN.3.91.1001228064021.19267B-100000@is>
MIME-Version:	1.0
X-MIME-Autoconverted:	from QUOTED-PRINTABLE to 8bit by delorie.com id XAA25270
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Please don't post in HTML.

On Wed, 27 Dec 2000, Alex Oleynikov wrote:

> Investigating the call frame traceback EIPs, I found that it is always
> function free(), who causes the exception, called from within on of the
> libraries (MGUI). Particularly, this line of code inside it:
> …
> <_free + 0xaa > mov %ecx, %ebx
> …
> 
> According to the exception info DJGPP shows, ecx =  00000000 at this moment.
> Does anybody know what may be the problem? Maybe the different libraries I
> am using are compiled with different versions of libc?

It's most probably some bug in your code whereby you overrun the end of 
an allocated buffer.  See section 9.2 of the DJGPP FAQ list for more 
details.

- Raw text -