C++ Debugging

systematic-debugging gives you the language-neutral method. This skill adds the native C++ toolchain and runtime techniques that matter once the bug involves crashes, corrupted memory, UB, or platform-specific debugger state.

When to Use

• A C++ process crashes with a segmentation fault, access violation, or abort
• The bug depends on object lifetime, ownership, or move/copy behavior
• Behavior changes between debug and release builds
• AddressSanitizer, UndefinedBehaviorSanitizer, or a debugger is needed to see the failure clearly
• A native test hangs, deadlocks, or corrupts memory without a clear stack trace

When NOT to Use