delorie.com/archives/browse.cgi | search |
From: | Matthew Mastracci <mmastrac AT acs DOT ucalgary DOT ca> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Memory leak. |
Date: | Fri, 3 Oct 1997 15:08:40 -0600 |
Organization: | The University of Calgary |
Lines: | 15 |
Message-ID: | <613mu2$15fa@ds2.acs.ucalgary.ca> |
References: | <3 DOT 0 DOT 16 DOT 19971003101449 DOT 36e7aec2 AT hem1 DOT passagen DOT se> |
NNTP-Posting-Host: | mmastrac AT acs2 DOT acs DOT ucalgary DOT ca |
Mime-Version: | 1.0 |
cc: | djgpp AT delorie DOT com |
In-Reply-To: | <3.0.16.19971003101449.36e7aec2@hem1.passagen.se> |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
On Fri, 3 Oct 1997, Peter Palotas wrote: > Could someone please give me a complete description of what a memory leak > really is? A memory leak is when allocated memory is not freed. I believe there's even a DJGPP library to check for these things (it used to be called Sentinel, but I don't remember its new name). /\/\att /\/\astracci mmastrac AT acs DOT ucalgary DOT ca GCS/GE d- s+:+ a--- C++++ UA P+ L E-- W+ N++ o K+ w+ O M- V PS++ PE++ Y+ PGP t+++ 5+++ X++ R++ tv+ b+++ DI++++ I G++ e h r* z?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |