cpp-systematic-debugger

A systematic C++ debugging workflow guides you through parsing issue tickets, reviewing suspect files, and progressively running sanitizers to gather evidence. It ensures traceability by maintaining an ongoing debug log for human-in-the-loop feedback.

Hypothesis-driven C++ debugging is a methodical process of testing each potential root cause with documented evidence and test plans. You parse a DEBUG_TICKET.md, investigate suspect code, and eliminate causes using sanitizer results and deterministic tests.

To start a systematic C++ debugging session, provide a DEBUG_TICKET.md in your project root and run the initialization script. This creates a new session log to begin investigating suspect code and running GTest or Catch2 tests.

Yes, the C++ debugging workflow integrates with memory debugging tools and sanitizers. It runs deterministic tests using GTest and Catch2, captures sanitizer results, and documents the findings to isolate root causes within your codebase.

Before starting C++ root cause analysis, you need a clearly formatted DEBUG_TICKET.md in the project root describing the problem. This ticket initiates the investigation workflow and creates an ongoing debug log for traceability.