From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Any other debuggers/resource tracers? Date: Sat, 22 Jan 2000 09:35:35 +0200 Organization: NetVision Israel Lines: 19 Message-ID: <38895DC7.26A47337@is.elta.co.il> References: <83zou0v5o6 DOT fsf AT mercury DOT st DOT hmc DOT edu> <388825BC DOT 23A6DFC7 AT is DOT elta DOT co DOT il> <869p9l$i88$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> NNTP-Posting-Host: ras1-p17.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 948526533 18955 62.0.172.19 (22 Jan 2000 07:35:33 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 22 Jan 2000 07:35:33 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker wrote: > > > >> 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. The FILE objects for the standard streams are static, but the buffers they use are not: they are malloc'ed the first time someone uses the stream, if the stream is buffered (take a look at src/libc/ansi/stdio/filbuf.c, for example). Nate explicitly mentioned the buffer used by the stream (see above), that's why I asked about the standard streams, which most programs never dream about closing.