Home/ Questions/Q 6716571
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T08:44:59+00:00

I have run my code through valgrind with these results: ==4492== Memcheck, a memory

  • 0

I have run my code through valgrind with these results:

==4492== Memcheck, a memory error detector
==4492== Copyright (C) 2002-2009, and GNU GPL’d, by Julian Seward et al.
==4492== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==4492== Command: ./mem
==4492== Parent PID: 4455
==4492==
==4492==
==4492== HEAP SUMMARY:
==4492== in use at exit: 0 bytes in 0 blocks
==4492== total heap usage: 19,595,342 allocs, 19,595,342 frees, 27,194,270 bytes allocated
==4492==
==4492== All heap blocks were freed — no leaks are possible
==4492==
==4492== For counts of detected and suppressed errors, rerun with: -v
==4492== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

However, while the code is running, I see a small, steady increase in the memory used by the program. How sure can I be with that result?

I run valgrind using:

valgrind --track-origins=yes --leak-check=yes
    --tool=memcheck --read-var-info=yes --log-file=error.txt`

and I compile the program using the -g and the -march=core2 tags.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You need to distinguish between memory leaks (memory that was allocated, but you lost all references to) and memory hogs (memory that was allocated, that you keep references to, but forgot to deallocate).

    The later one can not be detected by valgrind, since valgrind doesn’t know you did not want to use it anymore.

    To get some statistics about your programs memory usage, you can use the massif tool of valgrind, which will show you in more detail where your memory gets allocated. This might be helpful in finding memory hogs.

    • 0