Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!linus!linus!ccels3!rtidd
From: rtidd@ccels3 (Randy Tidd)
Newsgroups: comp.lang.c
Subject: Re: Just a minor new twist on free()
Message-ID: <121773@linus.mitre.org>
Date: 1 Oct 90 14:27:37 GMT
References: <7365@darkstar.ucsc.edu> <1990Oct01.020420.3401@virtech.uucp>
Sender: usenet@linus.mitre.org
Reply-To: rtidd@ccels3 (Randy Tidd)
Organization: The Mitre Corporation
Lines: 25

In article <1990Oct01.020420.3401@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
> 
> [ ... ]
>
>A while back I put together a debugging library for malloc and it's
>associated functions which was posted to comp.sources.unix back in may/june.
>This library purposely trashes data pointed to by the free'd pointer to 
>ensure that you aren't using a freed pointer (in addition to lots
>of other checks, like overrunning the amount of malloc data that you 
>asked for).
>
>If you are working with malloc'd data, you might want to get a copy of 
>the library.  It makes solving most malloc problem easy.

I checked comp.sources.unix on my news server and it doesn't have ANY
messages in it, much less the ones from may/june. If anyone has a copy
of the routines Conor talks about here, can they mail them to me?  I
tried mailing him directly but it bounced.

Thanks in advance!

Randy Tidd
rtidd@mwunix.mitre.org

"It's easier to get forgiveness than permission."