Re: newbie: can't read fast enough... :-) memory leaks...

[anon@att.net]

But the "free()" from the C-library or OS links does not fully reclaim 
memory and no other program can use this memory until the program ends. 
Unless, that memory is setup as a OS share resource.

That's why I said the programmer needs to modify these routines to add 
Garage Collection (GC), but any GC algorithm will slow the program down.

All of GNAT's memory/storage pools packages and Memory package has its 
pluses and its minuses.  Now, the Global and Local default pools allow 
dynamic allocation without using the Ada attributes. So modifying these 
packages a programmers can add monitor all programs allocations including 
the creation of static variables. While the others pools in GNAT use static 
or stack allocated data and can only monitor it own data.


Now it seams that the map for pools is

  Runtime pools
    Memory
      Pool_Global    --  no automatic reclaim
                     --  default pool for all storage

      Pool_Local     -- handles unbounded reclaim pool
                     -- reclaimed at pool finalization
                     -- uses System.Pool_Global 
                     -- default pool

      Pool_Size      --  stack bounded pool
                     --  reclaimed by normally stack management


  User defined pools
    Memory
      Storage_Pools  --  user defined static pool


  Undefined pools 
    Memory
      Pool_Empty     --  GNAT compiler does reference package

      Remote_Pools   --  comments in GNAT compiler which reference the 
                     --  Implementation Permissions of the
                     --  RM: Remote Call Interface Library Units
                     --  So, package is not included or fully supported 
                     --  in GNAT runtime


  Special pools
    Memory
      Checked_Pools  -- Similar to Storage_Pools with Dereference monitoring
      Debug_Pools    -- Package to help track down memory corruption 
                     -- uses Checked_Pools


In <lyr3zqh03t.fsf@pushface.org>, Simon Wright <simon@pushface.org> writes:
>anon@att.net writes:
>
>> The "Deallocation" routine is normally unfunctional so memory is
>> "reclaimed" during program finalization only.
>
>For GCC 4.9.0, Deallocate (both Pool_Global and Pool_Local) calls
>Memory.Free which calls free().