Modern Static Code Analysis the Example of PVS-Studio

on YouTube ↗09m

" summary

PVS-Studio is a static analyzer that uses semantic analysis and data-flow tracking (including interprocedural analysis and taint analysis) to find real bugs: copy‑paste condition errors, self‑assignment, deleting a void pointer, misuse of noexcept that can crash, and more. The team reports 14 historical instances of mistaken = vs == with the last seen in 2016. Integration options include Visual Studio, CLion, Qt Creator, VS Code, build systems (CMake/MSBuild) and CI tools like GitHub Actions and Jenkins; baseline and ratchet approach workflows manage existing warnings.

AI-written summary · about

" chapters (6)

1. 0:00Introduction
2. 0:33What is static analysis?
3. 2:17Analysis vs compilers
4. 4:50Real-world error examples
5. 6:46Integration strategies
6. 8:00Tooling and conclusion

" related talks

• 44mStatic analysis as an additional barrier against bugsSergey Khrenov · TestCon Moscow 2019
• 50mInside a static analyser: type systemYuri Minaev · NDC TechTown 2021
• 43mEverything I learned about static analysis and program safety in C++Sunny Chatterjee · Pure Virtual C++ 2022
• 36mCode Analysis: Empowering developers to write performant, reliable, and safe C++Sunny Chatterjee, Jim Radigan · Pure Virtual C++ 2021
• 50mPractical Advanced Static AnalysisDave Liddament · PHP UK Conference 2022
• 52mFinding Bugs Using Path-Sensitive Static AnalysisGabor Horvath · CppCon 2021
• 51mCode Analysis ++Anastasia Kazakova · NDC TechTown 2022
• 58mSecurity Static Analysis - Avoiding an Angry Mob of EngineersJosh Brown-White · NDC Oslo 2019