Valgrind
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
Why people recommend it
“that code will be tortured under valgrind. That’s non-negotiable in my book.”
“It's a really brilliant way to visualise what heap structures are using memory in C programs.”
Show 3 more
“Miri, Valgrid and the LLVM sanitizers all compliment each other and it's really worth adding all of them to a project if you can.”
“thankfully, using valgrind, then sanitisers in my build/test step makes this a very low priority for me.”
“Valgrind does need a lot of work, especially for missing CPU features and for Darwin.”
Caveats and dissent
“the lack of Valgrind support for many of the AVX512 instructions frustrates me almost daily”
Often compared with
Who recommends it in their own words
From the makers not counted in the ranking
“I dabble a little bit on arm64”
“Please give it a try in configurations that are important for you and report any problems you have”
Threads where it came up
- 11 year old unsoundness bugs found in Rust borrow checker 1 mention
- How Our Rust-to-Zig Rewrite Is Going 1 mention
- Twenty One Zero-Days in FFmpeg 1 mention
- Converting an Integer to a Decimal String in Under Two Nanoseconds 1 mention
- Valgrind 3.27 RC1 is out 1 mention
- Intel's make-or-break 18A process node debuts for data center with 288-core Xeon 1 mention
Data: valgrind.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 11
“that code will be tortured under valgrind. That’s non-negotiable in my book.”
“usage of Miri and Valgrind”
“C's tools for this like Valgrind, instrumented allocators and LLVM sanitizers work with Rust too.”
“the lack of Valgrind support for many of the AVX512 instructions frustrates me almost daily”
“while running the tools (e.g. evince) in valgrind”
“It's a really brilliant way to visualise what heap structures are using memory in C programs.”
“Miri, Valgrid and the LLVM sanitizers all compliment each other and it's really worth adding all of them to a project if you can.”
“thankfully, using valgrind, then sanitisers in my build/test step makes this a very low priority for me.”
“valgrind memory leak”
Yeah, it panics when you use after free. [1] But I'm not sure it's worth porting your code to Fil-C just to get that property. Because Fil-C still needs to track the memory allocation with its garbage collector. there isn't much advantage to even calling free. If you don't have a use-after-free bug, then it's just adding the overhead of marking the allocation as freed. And if you do have a use-after-free bug, you mig
“Valgrind does need a lot of work, especially for missing CPU features and for Darwin.”