From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,f3f3bded7ff60ce8
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Alex R. Mosteo" <devnull@mailinator.com>
Newsgroups: comp.lang.ada
Subject: Re: Memory profiling
Date: Fri, 27 May 2005 17:55:46 +0200
Message-ID: <42974302.5080908@mailinator.com>
References: <429717E8.6030806@mailinator.com>
 <wccll6066ao.fsf@shell01.TheWorld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net +AsZ2uBoz6R/2ULga/Xs/QoCv0Xt5w7D7VXQVgezO6QOv8wyk=
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language: en-us, en
In-Reply-To: <wccll6066ao.fsf@shell01.TheWorld.com>
Xref: g2news1.google.com comp.lang.ada:11186
Date: 2005-05-27T17:55:46+02:00
List-Id: <comp.lang.ada>

Robert A Duff wrote:
> "Alex R. Mosteo" <devnull@mailinator.com> writes:
> 
> 
>>I suppose something similar can be achieved using distinct storage pools
>>for each access type being tracked, but I find this more
>>inconvenient. Ummm, maybe a type holding a list of storage pools created
>>on demand...
> 
> 
> All those storage pools can share the same underlying memory pool.  That
> is, each pool just keeps track of whatever debugging/statistics info you
> want, and then calls some underlying pool, or just does a "new", or
> calls malloc, or whatever.  So gathering fine-grained (per type)
> information does not need to imply that you have to actually allocate
> type-segregated data.

That's the idea I had in mind, but you still have to provide a new 
storage pool for each tracked access type. Nonetheless, I see 
interesting potential in this idea.

In other news, I've just tested the Massif module of Valgrind and while 
it doesn't do exactly what I wanted, it is a very valuable tool. What it 
does is to keep track of all allocations, so it gives and idea of the 
overall story instead of a particular moment in time. It works 
out-of-the-box with gnat executables compiled with debug info.

And I just have recalled about gnatmem, silly me.