golang-troubleshootinglisted

# Go Troubleshooting Find the causal chain before recommending a fix. Keep diagnostic evidence, root-cause claims, and any subsequent code change distinct. ## Start with the Symptom Record expected behavior, actual behavior, exact error or stack, frequency, environment, inputs, first known bad version, and recent relevant changes. Preserve raw evidence before reducing it to a theory. Route by symptom: | Symptom | First evidence | Reference | | --- | --- | --- | | Compile, link, module, CGO, or build-tag failure | Exact build command and complete diagnostics | [references/compilation.md](references/compilation.md) | | Wrong output or panic | Minimal reproduction, full stack, data-flow trace | [references/common-go-bugs.md](references/common-go-bugs.md) | | Intermittent failure, race, hang, or goroutine growth | Repetition, race detector, goroutine dump or trace | [references/concurrency-debug.md](references/concurrency-debug.md) | | Slow, high CPU, memory growth, or contention | Profile or trace from representative load | [references/performance-debug.md](references/performance-debug.md) | | Failing or flaky test | Isolated command, cache/order/parallel controls | [references/testing-debug.md](references/testing-debug.md) | | Live incident | Existing telemetry and authorized low-risk capture | [references/production-debug.md](references/production-debug.md) | Use [references/methodology.md](references/methodology.md) for the shared investigation loop. ## Investigation R