Re: RAM consumption when working with the gcc repo

On Dec 7, 2007 9:46 PM, Nicolas Pitre <nico@cam.org> wrote:

BTW does exist a tool to profile memory consumption by each source level struct / vector/ or any other data container?

Valgrind checks mainly memory leaks, callgrind gives profiling information in terms of call graphs and times/cycles consumed by each function.

What I _really_ would like it's a tool that allows me to *easily* check how much memory is used in a given point in time by each data container at source level.

Something like this:

At checkpoint "trigger_now":

struct my_data is instantiated 120234 times struct super_delta is instantiated 100000 times

At checkpoint "trigger_also_now":

struct my_data is instantiated 12 times struct super_delta is instantiated 70 times

.....

That would be AWSOME!!! a super debugging killing tool!

Thanks Marco