From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Any other debuggers/resource tracers?
Date: 20 Jan 2000 12:39:37 -0800
Organization: InterWorld Communications
Lines: 21
Message-ID: <83zou0v5o6.fsf@mercury.st.hmc.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000120092446 DOT 21977S AT is>
NNTP-Posting-Host: mercury.st.hmc.edu
X-Trace: nntp1.interworld.net 948400884 7489 134.173.45.219 (20 Jan 2000 20:41:24 GMT)
X-Complaints-To: usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date: 20 Jan 2000 20:41:24 GMT
X-Newsreader: Gnus v5.7/Emacs 20.4
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes:

> On Thu, 20 Jan 2000, Andy wrote:
> 
> > Is there any good programs to detect memory leaks, files left open,unfreed
> > memory!
> 
> Try YAMD, its URL is in the FAQ.  It finds problems with using memory.
> 
> I'm not aware of any tool to find files left open (it's not a bug, in 
> most cases, since all open files are automatically closed by the exit 
> code).  If you really need that, you can define a function that will be 
> called on exit for each unclosed file handle.

YAMD will in some cases.  If using fopen and buffered streams, it will
notice that the buffer was allocated and not freed (i.e. fclose).  But
not explicitly.
-- 

Nate Eldredge
neldredge AT hmc DOT edu