2020: The Year of Sanitizers?
summary
Shows how ASan on Visual Studio 2019 actually gets enabled for MSVC projects and what the compiler plus runtime do to instrument code. Measures runtime costs and memory overhead on real projects, and demonstrates concrete diagnostics for use-after-free and out-of-bounds reads with Visual Studio memory snapshots that pinpoint stack/heap locations. Ends with a working pipeline that spins Azure fuzzing jobs against instrumented unit tests so many inputs find bugs automatically.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 15:23Dynamic analysis introduction
- 22:14Sanitizers in practice
- 31:50Case studies and demos
- 40:40Advanced tools and techniques
- 50:24Q&A and closing remarks
related talks
36mCode Analysis: Empowering developers to write performant, reliable, and safe C++
16mSEMSAN: a Configurable Sanitizer for Detecting System-Level Semantic Bugs
38mKernel Sanitizers Office Hours
26mUndefined Behavior in 2017 (part 2 of 2)
24mWhy you should be using automated fuzzing to test for security issues in your code
09mModern Static Code Analysis the Example of PVS-Studio
06mLightning Talk: You Should Use AddressSanitizer
59mHardening Your Code