From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Prevent crash on free()
Date: 28 Feb 2000 16:17:26 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 16
Message-ID: <89e72m$hpt$1@nets3.rz.RWTH-Aachen.DE>
References: <89e5e3$8g1$1 AT cubacola DOT tninet DOT se>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 951754646 18237 137.226.32.75 (28 Feb 2000 16:17:26 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 28 Feb 2000 16:17:26 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Marcus <mesthlm AT hem DOT passagen DOT se> wrote:

> How can I test if a memory is permanently alloced with malloc? To prevent
> crash on free().
[...]
> Because the program crash if I use free careless.

That's the wrong attitude towards the problem. Don't use free()
carelessly, and it won't crash on you. You're asking us how to cure
the symptoms, instead of how to fix the disease they tell you about.

Use YAMD or a similar tool to *find* the bugs in your program, instead
of trying to work around the valuable error messages they cause.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.