Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!uxh.cso.uiuc.edu!unicorn
From: unicorn@uxh.cso.uiuc.edu (Harry E Miller)
Newsgroups: comp.lang.c
Subject: Re: balancing free() and malloc()
Message-ID: <1991Jun24.151512.7586@ux1.cso.uiuc.edu>
Date: 24 Jun 91 15:15:12 GMT
References: <1991Jun22.173609.28393@cbnewsl.att.com> <820001@hpcuhc.cup.hp.com>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 14

rags@hpcuhc.cup.hp.com (Balakrishna Raghunath) writes:

>"memory leaks" has recieved much attention in the press. I just happen to have
>one of the journals lying on  my desk. Dr. Dobb's journal August 1990 
>(special issue on C programming).  An interesting and easy to implement 
>method for detecting memory leak is discussed.  

This is a very usefull article, the code that comes with it is very, very
usefull.  Somewhere buried under all the junk on my desk are two more
DDJ articles (August 1989 & May 1990) that have memory management routines
that look usefull, but I have not implemented them as of yet.

Harry E. Miller - "The Nine-Fingered Bandit"
unicorn@uxh.cso.uiuc.edu