| delorie.com/archives/browse.cgi | search |
| Date: | Thu, 20 Jan 2000 09:26:40 +0200 (IST) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Andy <a DOT pelton AT dtn DOT ntl DOT com> |
| cc: | djgpp AT delorie DOT com |
| Subject: | Re: Any other debuggers/resource tracers? |
| In-Reply-To: | <865kqu$bq0$1@nclient3-gui.server.dtn.ntl.com> |
| Message-ID: | <Pine.SUN.3.91.1000120092446.21977S@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | dj-admin AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
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.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |