Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!mips!atha!aunro!alberta!brazeau.ucs.ualberta.ca!unixg.ubc.ca!ubc-cs!uw-beaver!zephyr.ens.tek.com!tektronix!reed!minar
From: minar@reed.edu
Newsgroups: comp.os.msdos.programmer
Subject: Re: Borland C++'s "heapcheck" function
Message-ID: <m0jizjG-0001OzC@dharma.reed.edu>
Date: 31 May 91 03:00:49 GMT
References: <0094956C.49369EA0@MAPLE.CIRCA.UFL.EDU> <1991May30.090835.9320@uwovax.uwo.ca>
Sender: nobody@reed.UUCP
Organization: Reed College, Portland, OR
Lines: 7

In article <1991May30.090835.9320@uwovax.uwo.ca> 35004_240@uwovax.uwo.ca (Charles McClellan) writes:

>These functions will basically catch most cases where you continue
>to use a pointer after freeing it.  Heapfillfree and heapcheckfree will also 
>catch memory overwrites of the heap.

how does it do that? What does it do, exactly?