systematic-debugging

Diagnose high CPU usage and memory leaks by mapping observed symptoms to likely causes and gathering targeted log evidence. Bounded log reading with tail and grep isolates relevant runtime anomalies for accurate root-cause identification.

Investigate intermittent runtime errors and process hangs by mapping observed symptoms to likely causes and testing hypotheses against evidence from stack traces and recent changes. This systematic approach prevents guessing and ensures accurate root-cause identification.

Analyze stack traces and error logs without exceeding token limits by using bounded log reading. This technique reads only relevant portions of logs using tail and grep to stay token-efficient during error investigation and diagnostics.

Format a structured bug report for build and test failures by producing a concise two-part report. This includes a summary and a detailed thread to ensure clear communication of the root-cause analysis and diagnostic evidence.

Diagnosing performance bottlenecks without source code access is possible if you have logs, stack traces, and recent change records. Systematic debugging relies on gathering evidence from these runtime artifacts rather than direct code inspection.

Your debugging process relies on guessing when you skip symptom-to-hypothesis mapping and bounded log reading. Systematic diagnostics require gathering evidence from stack traces and recent changes to ensure accurate root-cause identification without assumptions.