Re: [Valgrind-users] Profiling memory

[Nicholas N. <nj...@cs...>]

On Thu, 29 May 2008, Paulo Moura Guedes wrote:

> I can see in massif output where the majority of the memory is allocated.
> Though, I'm pretty sure those objects get destroyed after a while as they go
> out of scope (they were allocated on the stack, new operator was not used),
> but my application memory keeps groing. I would need to find out (filter) the
> allocations which are not deallocated as time goes by. Any ideas on how to
> find this information?

Massif takes periodic snapshots of memory.  If the size of the snapshots is
larger in the later snapshots, then that indicates a possible leak, and the 
info in the snapshots should give you a fair idea of where that is.  Are you 
sure you've understood Massif's output?  It might be worth experimenting 
with a smaller test program.

Also, if you use --stacks=yes Massif will do stack profiling as well (and 
run slower as a result).

Nick