root-cause-tracing

Root-cause tracing traces bugs backward through the call stack to identify the original source of invalid data or incorrect behavior, rather than just fixing the symptom. Start by examining where the error manifests, then work backward through each function call to locate where bad data first entered the chain.

Use instrumentation—such as stack traces and debug logs—when the call stack is too long or complex for manual tracing alone. Instrumentation provides diagnostic visibility into intermediate function calls, helping you pinpoint the exact point where behavior diverged from expected.

Root-cause tracing includes techniques and scripts to systematically identify which specific test or code block introduced bad state. Use polluter identification to isolate the source of environment pollution, then trace backward to fix the root trigger rather than just cleaning up afterward.

Yes. Root-cause tracing is designed for errors occurring deep in execution where the call stack is long and the root cause cannot be inferred from the symptom alone. It applies to both runtime failures and test scenarios with complex, layered execution paths.

Fixing where an error occurs addresses the symptom and prevents immediate failure, but the root cause may trigger the same bug again elsewhere. Root-cause tracing ensures fixes target the original trigger—such as an empty variable or invalid state—preventing recurring bugs and wasted debugging effort.