Build, Debug, and Test

Compile with warnings, debug with symbols, and use sanitizers to catch bugs early. Bad tooling setup is how bugs survive for weeks that should have been caught in minutes. In ~12 minutes you'll build a repeatable local workflow — compiler flags, debug symbols, sanitizers, and a CMake loop — that catches the problems most developers don't find until production. ─── What You'll Learn ─────────────────────────────────────── ✔ The compiler flags every project should start with (-Wall, -Wextra, -Wpedantic) ✔ Debug symbols and why you turn off optimization while diagnosing ✔ AddressSanitizer and UndefinedBehaviorSanitizer — what they catch and how to run them ✔ A complete one-liner build command for small projects ✔ The CMake + Ninja + ctest loop that scales to larger codebases ✔ A 5-step debugging process that works on any size bug ✔ Sanitizer strategy — why you run them in separate builds ✔ CMake presets worth having: Debug, AsanUbsan, Release ✔ Small habits that make bugs reproducible and fixable faster ─── Chapters ──────────────────────────────────────────────── 0:00 Intro 0:38 Compiler flags 1:32 Debug symbols & sanitizers 2:54 Command-line workflow 3:53 Testing advice 4:47 CMake build loop 5:41 Debugging loop 6:48 Sanitizer strategy 7:54 CMake presets 9:07 Better bug reports 10:11 Small but important habits 11:19 What's next ─── Resources ─────────────────────────────────────────────── 📘 Modern C++ Complete Reference Handbook → https://cpp-handbook.cc ─── Series ────────────────────────────────────────────────── This video is part of the Complete C++ Guide — Advanced Series. If this helped, subscribe — new videos drop every week.