“The Current State of (free) Static Analysis"
summary
Survey of free tools (Cppcheck, Clang static analyzer, Visual Studio analyzer, Coverity Scan, Metrics++, copy‑paste detector) compares real failures: several analyzers miss assert with side effects, many miss lambdas that capture a dangling reference, and only Coverity flags mixed‑vector iterator misuse; Cppcheck finds empty vector loops and clang‑modernize recommends range‑for to avoid size_t/int truncation bugs. Sanitizers and fuzzing later find ~15 crashes in one project, so tools help but leave false negatives and platform‑dependent failures (use many tools and warnings).
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:52Static Analysis
- 1:23Compiler Warnings
- 1:54CVPCheck
- 2:49What is wrong
- 3:26Tools
- 3:42Uni
- 5:00X
- 7:12clang
- 7:42Google
- 8:40Go
- 9:32Null pointer
- 10:37Smart pointer
- 11:13C style arrays
- 12:26Capture by reference
- 14:18STD Move
- 17:50Hither Raters
- 18:46Metrics Plus
- 19:45CopyPaste Detector
- 20:31Warnings
- 22:36False Sense of Security
- 23:41RealWorld Example
- 24:10Conclusion
- 25:06Warning Levels
- 25:55Writing Your Own Analysis
- 26:47CVP Check
related talks
52m“Tools from the C++ eco-system to save a leg”
36mThings I learned from the static analyzer
01h 01mMake Friends with the Clang Static Analysis Tools
01h 01mCode Analysis++
43mEverything I learned about static analysis and program safety in C++
01h 03m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (2 of 2)”
51mCode Analysis ++
01h 00mAdvanced Tools for Better Productivity
