investigate

To find the root cause of a bug, you need to systematically collect error messages, stack traces, and code diffs to form testable hypotheses. This approach enforces disciplined debugging by gathering evidence before proposing changes.

Reproducing an issue across environments involves analyzing git history, patches, and logs to validate hypotheses. By tracking code changes and comparing runtime data, you can reliably isolate the specific commit or condition triggering the defect.

To propose a concrete bug fix with regression tests, you first verify your hypothesis by reproducing the issue. You then implement the code correction and add corresponding tests to prevent the same defect from recurring in future changes.

Yes, you can use bash and grep to gather logs and code evidence for debugging. These tools allow you to search through codebases and runtime data to collect the stack traces and error messages needed for root-cause analysis.

Systematic root-cause debugging works across different codebases by applying standard evidence gathering and hypothesis verification techniques. It relies on analyzing logs and code behavior rather than language-specific features, making it broadly applicable.

You should gather stack traces and error messages before writing a code fix to avoid symptom-based patches. Collecting this evidence first ensures you understand the underlying failure mechanism and can implement a verifiable solution.