AddressSanitizer on Windows
summary
AddressSanitizer is available in Visual Studio (stable since 16.9) and finds real heap, stack and container overflows that static checks miss, with typical slowdowns around ~2x runtime and about 2x memory for heap-heavy apps. Integration produces portable snapshot (.dmp) files that open in the debugger’s memory window, and pairs with Azure OneFuzz for cloud fuzzing. Gotchas: edit‑and‑continue, incremental linking, /NODEFAULTLIB and RTC checks are incompatible until workarounds or newer builds are used.
AI-written summary · about
chapters (12)
- 0:00Introduction to testing
- 1:08AddressSanitizer on Windows
- 3:16The importance of tooling
- 6:03Static analysis techniques
- 15:24Clang support in Visual Studio
- 19:16Static vs dynamic analysis
- 27:22Using AddressSanitizer
- 36:16Asan IDE integration
- 43:45How AddressSanitizer works
- 57:06Asan implementation details
- 1:06:55Debugging examples
- 1:17:26Fuzzing and conclusion
related talks
50mC++ Sanitizers & Fuzzing for the Windows Platform Using New Compilers...
40mAddressSanitizer, or How to Make C/C++ Programs More Reliable and Secure
36mCode Analysis: Empowering developers to write performant, reliable, and safe C++
06mLightning Talk: You Should Use AddressSanitizer
50mAddressSanitizer/ThreadSanitizer for Linux Kernel
59mBeyond Sanitizers...
01h 02mSanitize your C++ code
49mTeaching Containers and Allocators How to Sanitize Addresses
