Re: [Valgrind-users] Results conflict while leak-check flags set to summary and yes ?

[Nicholas N. <n.n...@gm...>]

On Tue, Mar 17, 2009 at 7:23 PM, Imhexyl Imhexyl <im...@gm...> wrote:
>
> I used Memcheck to check a simplest glib program listed below. While I set
> leak-check flag to summary, the detector showed me 20 blocks possibly lost.
> Confusing, while I set leak-check flag to yes or full in order to get
> details of these leaks, the detector showed me 20 blocks suppressed instead
> of 20 blocks possibly lost, though the number of suppressed errors was not
> changed. Which report I should belive?

Believe the --leak-check=full flag.

I recently fixed this variation in behaviour on the trunk.  Here's the
description that will be in the NEWS file of 3.5.0:

* Memcheck's leak checker has been improved.
  - The results for --leak-check=summary now match the summary results for
    --leak-check=full.  Previously they could differ because
    --leak-check=summary counted "indirectly lost" blocks and "suppressed"
    blocks as "definitely lost".


Nick