C
You're viewing a free preview. Sign in free to read every script.
Why this exists The debugging page finds bugs by running the program under Valgrind or a sanitizer. That only finds bugs on the paths your test actually takes, and error paths are exactly the ones nobody tests. Static…
Static Analysis in CI: Compiler Warnings, -fanalyzer, cppcheck and a Lint Gate
Find memory bugs without running the program. See what compiler warnings, GCC's -fanalyzer and cppcheck each catch (and miss) on real buggy code, then wrap them in a lint script that fails a CI pipeline.
Sign in free to read this script, along with the rest of the library.
Sign in free