golang-troubleshooting

Debugging a hanging Go program requires reproducing the issue and using pprof goroutine profiling or GODEBUG tracing to identify blocked goroutines. This evidence-first workflow traces the deadlock to its exact origin before attempting any fix.

Finding the root cause of a Go panic requires reading the error stack trace, reproducing the failure reliably, and using Delve to step through the crashing code path. This method ensures you fix the actual origin instead of patching surface symptoms.

Diagnosing high CPU usage or memory growth in a Go service involves capturing pprof heap and CPU profiles during the spike. You measure the specific resource allocation to trace backward to the inefficient code block before applying any optimizations.

Yes, you can use the go test -race command to detect data races and concurrency issues in Go. It is a core diagnostic tool for identifying flaky behavior by highlighting unsafe concurrent memory access during test reproduction.

Use Delve for stepping through logic errors and panics to inspect variable state, while pprof is for diagnosing performance issues like high CPU, memory growth, and deadlocks. Choose the tool based on the specific failure mode being investigated.