From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Any other debuggers/resource tracers?
Date: 21 Jan 2000 14:08:53 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 21
Message-ID: <869p9l$i88$1@nets3.rz.RWTH-Aachen.DE>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000120092446 DOT 21977S AT is> <83zou0v5o6 DOT fsf AT mercury DOT st DOT hmc DOT edu> <388825BC DOT 23A6DFC7 AT is DOT elta DOT co DOT il>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 948463733 18696 137.226.32.75 (21 Jan 2000 14:08:53 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 21 Jan 2000 14:08:53 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

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> Nate Eldredge wrote:
>> 
>> Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes:
>> 
>> > I'm not aware of any tool to find files left open
>>
>> 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.

> Does this mean that YAMD always produces diagnostic messages about stdin and
> stdout?

No, as those are statically present objects inside the library. But
each file opened via fopen() has an malloc()ed FILE structure with
it. If not fclose()d properly, that malloc()ed block should trigger as
a memory leak.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.