stack-trace-go-probe

Start by identifying the package and symbol in the trace, then check for nil pointer dereferences, unhandled error returns, and goroutine boundary issues. Reproduce the failure with a narrow go test ./path -run TestName command before patching.

Write a minimal test targeting the failing function and run it with go test ./path -run TestName. Narrow test commands isolate the failing package or symbol exposed in the stack trace.

Nil pointer dereferences occur when code accesses fields or methods on a nil pointer, often from unchecked error returns or missing nil guards. Adding explicit nil checks and error handling at the identified patch targets prevents them.

No. The probe only returns checks, reproducer commands, patch targets, and verification commands as text. It explicitly avoids suggesting any mutation of production state.

Use narrow go test ./path -run TestName commands when the stack trace exposes a specific package or symbol. This isolates the failure faster and avoids running unrelated tests during reproduction.