It’s Valgrind’s fault. First, -fsanitize=leak does not show anything. Second, Valgrind itself states that: First of all: relax, it’s probably not a bug, but a feature. Many implementations of the C++ standard libraries use their own memory pool allocators. Memory for quite a number of destructed objects is not immediately freed and given back to … Read more
For anyone else who is still interested in graphical output of Massif from Valgrind please consider massif-visualizer, it is beautiful. You can find the project page at KDE-Apps. For Ubuntu you should build massif-visualizer from source or install package from Kubuntu-ppa repo: add-apt-repository ppa:kubuntu-ppa/backports apt-get update && apt-get install massif-visualizer
Valgrind basically runs your application in a “sandbox.” While running in this sandbox, it is able to insert its own instructions to do advanced debugging and profiling. From the manual: Your program is then run on a synthetic CPU provided by the Valgrind core. As new code is executed for the first time, the core … Read more
It just means that the permissions changed on a particularly large block of memory. That can happen because of something like a call to mprotect or when a very large memory allocation or deallocation occurs – an mmap or munmap call for example. The first one you list is setting about 320Mb of memory to … Read more
In C++ classes/structs are identical (in terms of initialization). A non POD struct may as well have a constructor so it can initialize members. If your struct is a POD then you can use an initializer. struct C { int x; int y; }; C c = {0}; // Zero initialize POD Alternatively you can … Read more
As there’s no stable release that supports Yosemite, you can install the latest development version with brew install –HEAD valgrind
valgrind –log-file=”filename”
There is more than one way to define “memory leak”. In particular, there are two primary definitions of “memory leak” that are in common usage among programmers. The first commonly used definition of “memory leak” is, “Memory was allocated and was not subsequently freed before the program terminated.” However, many programmers (rightly) argue that certain … Read more
Use the valgrind option –track-origins=yes to have it track the origin of uninitialized values. This will make it slower and take more memory, but can be very helpful if you need to track down the origin of an uninitialized value. Update: Regarding the point at which the uninitialized value is reported, the valgrind manual states: … Read more
As jakobengblom2 pointed out, valgrind has a suit of tools. Depending which one you are talking about there are different windows counter parts. I will only mention OSS or free tools here. 1. MemCheck: Dr. Memory. It is a relatively new tool, works very well on Windows 7. My favorite feature is that it groups … Read more