On 16/09/16 17:37, Nicholas Lamb wrote:
> I suppose the advantage of Massif is that it reveals the breakdown
> of heap memory distribution, so you can know how much memory is taken
> by accessible but unreleased blocks. I'm using a variant of the Eclipse
> IDE that provides good visualization of M
On Fri, 2016-09-16 at 15:37 +, Nicholas Lamb wrote:
> I think Memcheck actually can say something about accessible but unreleased
> blocks, but by default it doesn't.
> The show-leak-kinds option, according to the Valgrind manual, can contain the
> 'reachable' value. In this case,
> Memchec
From: Julian Seward [mailto:jsew...@acm.org]
Sent: Friday, September 16, 2016 4:35 AM
To: Nicholas Lamb ; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Using Massif to find space leaks
This is all a bit cryptic, but what it means is: Memcheck will tell you about
leaks whe
This is all a bit cryptic, but what it means is: Memcheck will tell you
about leaks where all pointers to a block are lost, so it can never be
freed. But it doesn't say anything about a different kind of leak, in
which blocks are continuously allocated over the lifetime of the program,
but only e
In the Valgrind User Manual, the Massif chapter mentions:
"certain space leaks ... aren't detected by traditional leak-checkers, such as
Memcheck's. That's because the memory isn't ever actually lost -- a pointer
remains to it -- but it's not in use. ... Massif can help identify these leaks."
Th
