Date:	Sun, 15 Dec 2002 00:08:32 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	"Lars O. Hansen" <lars DOT o DOT hansen AT gmx DOT de>
Message-Id:	<3277-Sun15Dec2002000831+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<atfirg$1j4$1@news.online.de> (lars.o.hansen@gmx.de)
Subject:	Re: problem with malloc and free
References:	<000001c2a37a$59f41060$186a10ac AT citechbd DOT com> <atfimi$1fk$1 AT news DOT online DOT de> <atfirg$1j4$1 AT news DOT online DOT de>
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

> From: "Lars O. Hansen" <lars DOT o DOT hansen AT gmx DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 14 Dec 2002 16:30:55 +0100
> >
> > Call frame traceback EIPs:
> >   0x00003825 _free+77
> >   0x000018bb _freeall+99
> >   0x0000353f _exit+31
> >   0x0000171f _main+31
> >   0x00003138 ___crt1_startup+176
> 
> also as you can see in the traceback in Re to Richard, it crashed in
> the first free. So free is somehow the problem.

Crashes inside `free' or `malloc' usually mean that your program
overwrites buffers allocated with `malloc' and thus destroys hidden
data about the heap stored by `malloc' at both ends of the buffer it
allocates.

So you need to look for such bugs in your program.

- Raw text -