debugging-guidelisted

# Debugging Guidelines Systematic, hypothesis-driven debugging of native/low-level software, plus designing each class of bug out of existence. The cheapest bug is the one made impossible; the next cheapest is the one that trips a tripwire the instant it happens. Lifetime/ownership design lives in memory-management-guide, race correctness in lock-free-guide, and speed profiling in data-oriented-design-guide; this skill is about finding bugs and preventing classes of them. ## Essentials - **Classify the bug** - Each class (logic, uninitialized, leak, overwrite, race, design, intermittent) has a design choice that eliminates the whole class, see [references/bug-taxonomy.md](references/bug-taxonomy.md) - **Hypothesis, not flailing** - Form one falsifiable guess, change one thing, predict, observe; never edit randomly, see [references/scientific-debugging.md](references/scientific-debugging.md) - **Get a deterministic repro first** - A reliable repro is what lets you step through the "before"; shrink it small, see [references/reproduction-and-bisection.md](references/reproduction-and-bisection.md) - **Trip the wire early** - Assertions, invariants, validation layers, and sanitizers turn silent corruption into a loud failure at the fault site, see [references/instrumentation-and-checks.md](references/instrumentation-and-checks.md) ## Find the cause - **Bisect to the change** - With a 100% repro, search history for the commit that introduced the bug, see [references/reproducti