Re: [Valgrind-developers] Memory allocation reporter

[Nir T. <nir...@gm...>]

On Mon, Nov 30, 2009 at 2:49 PM, Josef Weidendorfer
<Jos...@gm...> wrote:
> Am Sonntag 29 November 2009 09:20:14 schrieb Nir Tzachar:
>> Hello.
>>
>> I have been using valgrind for a very long time, and found it one of
>> the best (if not The Best) debugging and bug finding tools ever. I
>> have even ported applications from other archs to linux just to be
>> able to run them through valgrind and track an elusive bug.
>>
>> However, there is one point where valgrind does not scratch my itch:
>> reporting memory allocations. I have searched through the
>> documentation, and did not find any way to report all the locations
>> where memory is allocated.
>
> Sorry for my blatant ignorance for your use case.
> What are the features missing from, e.g. massif, to fit your needs?

Well, I do not care about the _total_ memory consumption, just the
allocations themselves. Usually, I use memory pools, and just allocate
from them. I do not care if they are large (I do, but this is another
issue), but that _all_ code paths really use the pools and do not hide
any unknown allocation behind the scenes.

If massif can just report where ALL allocations are taking place and
be able to suppress some of them, I would be a happy camper ;)