Everything I learned about static analysis and program safety in C++
summary
Sees C++ memory safety as the main problem—uploader cites 70% of serious security bugs from memory issues—and shows static analysis deployed in Visual Studio, GitHub Actions and Compiler Explorer finding real defects: lint-style checks catching union type confusion, intra-procedural checks plus SAL annotations revealing a buffer-overrun, and adoption of GSL span to encode pointer+size so runtime checks can prevent overruns. Team reports a ~45% analyzer speedup and fixed 1,000+ static-analysis bugs in Visual Studio during a recent push.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:14C++ code safety: Why it matters?
- 3:26Static code analysis: Why and what?
- 7:55Ideal way to "shift left" in GitHub
- 10:38Lint style checks
- 15:39Challenge: Scaling Lint-style checks
- 26:29Join the fun
- 28:04What's next for code analysis?
- 33:26Connect with us
related talks
01h 00mStatic Analysis and Program Safety in C++: Making it Real
36mCode Analysis: Empowering developers to write performant, reliable, and safe C++
01h 01mClosing the Gap between Rust and C++ Using Principles of Static Analysis
01h 28mKeynote: Safety, Security, Safety and C / C++ - C++ Evolution
01h 04mC++ and Safety
29m“The Current State of (free) Static Analysis"
01h 06mmemory-safe C++
01h 03mLifetime Safety in C++: Past, Present and Future