8 engineers on Hacker News describe using Valgrind first-hand: 3 endorse it, 2 regret it, 0 are mixed.
“One of them has been used in production for 5+ years without a single bug. The trick is to do it very carefully and use automatic tools (Valgrind etc.) to verify the code.”
endorse · production · 5 yr · deterministic · 2026-10-24 · source ↗ · wrong label?“valgrind can also do most of the same checks, but is much slower. On my team we use both”
endorse · production · wallstprog · 2022-12-06 · source ↗ · wrong label?“Valgrind was THE tool that saved our as*s day after day after day.”
endorse · production · lma21 · 2022-07-27 · source ↗ · wrong label?“valgrind is a tremendously slow way to do one-off debugging of a suspected memory leak.”
regret · production · thrownaway2424 · 2014-11-11 · source ↗ · wrong label?“Valgrind was always too expensive but using ASAN builds we can find more bugs.”
regret · production · xyzzy123 · 2012-11-03 · source ↗ · wrong label?“runs cppcheck, uploads to a container, and runs it with valgrind.”
neutral · personal · ActorNightly · 2025-12-10 · source ↗ · wrong label?“we run valgrind on them, they are fully integrated with GCC and autotools”
neutral · production · rwmj · 2018-11-26 · source ↗ · wrong label?“I've had bigger stuff already pass the "no leaks are possible" certification”
neutral · production · joshguthrie · 2013-12-06 · source ↗ · wrong label?