3 ms·
Valgrind doesn't require rebuilding the program, which is useful. Valgrind will detect the problem even in assembly code. E.g. if your inline assembly code uses
by kazinator 5y ago
Valgrind doesn't require rebuilding the program, which is useful. Valgrind will detect the problem even in assembly code. E.g. if your inline assembly code uses uninitialized data, or accesses a heap object out of bounds, Valgrind will show that.
Valgrind is usable for finding problems in code that isn't 100% conforming with ISO C in its use of memory. For instance, it usefully refrains from complaining when a conservative garbage collector treats the entire stack as an array of pointers to scan for object graph roots.