[Valgrind-users] Valgrind with and without stack provide different result

[Bastien M. <bas...@gm...>]

Hi,

I am prety new to valgrind. I mainly use memcheck, sgcheck and massif.

As I want to check stack and heap memory usage of a binary I use massif and
found something weird to me :

I used `valgrind --tool=massif --time-unit=B --peak-inaccuracy=0.1
--threshold=0.1 --detailed-freq=1 --max-snapshots=1000
--massif-out-file="my/math/massif.out" my_binary to get a heap profile. The
last snapshot was the following :
--------------------------------------------------------------------------------
  n        time(B)         total(B)   useful-heap(B) extra-heap(B)
stacks(B)
--------------------------------------------------------------------------------
747      1,828,928                0                0
0            0

So all was fine. Then I tryed with --stacks=yes and got this :
--------------------------------------------------------------------------------
  n        time(B)         total(B)   useful-heap(B) extra-heap(B)
stacks(B)
--------------------------------------------------------------------------------
856     78,076,000            2,256            1,040             8
1,208

I don't understand why this time the useful and extra heap does not fall to
0 even if it is the same binary.

Some explanation would be very helpful and welcome :)

Regars.