Root Cause Tracing

Overview

Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom.

Core principle: Trace backward through the call chain until you find the original trigger, then fix at the source.

When to Use

Use root-cause-tracing when:

• Error happens deep in execution (not at entry point)
• Stack trace shows long call chain
• Unclear where invalid data originated
• systematic-debugging Phase 1 leads you here

Relationship with systematic-debugging:

• root-cause-tracing is a SUB-SKILL of systematic-debugging
• Use during systematic-debugging Phase 1, Step 5 (Trace Data Flow)