This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: FREE touble

From: "John (Eljay) Love-Jensen" <eljay at adobe dot com>
To: <johny at softvation dot com>, <gcc-help at gcc dot gnu dot org>
Date: Fri, 10 Aug 2007 05:01:20 -0700
Subject: RE: FREE touble
References: <40453.125.160.176.131.1186738303.squirrel@webmail.softvation.com>

Hi Johny,

You are using the wrong tool to monitor the size of allocated memory and available memory in the free memory pool.

The tool you are using monitors consumed OS memory extents, but does not tell you how much available memory is in the free pool nor how much memory is current allocated from the free pool.

The free pool (used by malloc) doles out memory from OS memory extents.  Depending on your OS, the acquisition of OS memory extents may be explicit (such as OS/2 or Amiga), or implicit (such as most Unix-ish operating systems).

HTH,
--Eljay

References:
- FREE touble
  - From: johny

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]