cvs.gedasymbols.org/archives/browse.cgi | search |
From: | sparhawk AT eunet DOT at (Gerhard Gruber) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Remaining memory under OS/2 question |
Date: | Mon, 31 Aug 1998 12:23:55 GMT |
Organization: | EUnet Austria |
Lines: | 25 |
Message-ID: | <35eb853a.16135542@news.Austria.EU.net> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 980831121628 DOT 22974W-100000 AT is> <35eb49be DOT 27826391 AT news> |
NNTP-Posting-Host: | e209.dynamic.vienna.at.eu.net |
Mime-Version: | 1.0 |
NNTP-Posting-Date: | 31 Aug 1998 12:25:38 GMT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Destination: fesenko AT pacific DOT net DOT sg (Victor) From: Gruber Gerhard Group: comp.os.msdos.djgpp Date: Tue, 01 Sep 1998 01:14:05 GMT: >That means there is no way to determine the remaining physical memory. >But is there a way to find the amount of used memory then? That was >actually a real purpose of checking remaining memory. I was looking >that the remaining memory didn't go too low. If it did it meant I had >memory leaks somewhere. And how would you know that the shifting remaining memory is due to your program and from others? In a multitasking environment you could get different results each time you check how much memory is available so this is not a good approach to check for memory leaks. -- Bye, Gerhard email: sparhawk AT eunet DOT at g DOT gruber AT sis DOT co DOT at Spelling corrections are appreciated.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |