Find the nil deref a print loop can't catch
언제 쓸까: A specific input causes a panic and you can't see where without a debugger.
사전 조건
- Server/skill installed and authenticated — See repo README
흐름
-
Reproduce under debuggerUsing the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ 복사됨→ Process paused at the panic
-
InspectPrint locals and the call chain. Show me which variable is nil.✓ 복사됨→ Variable value + caller chain
결과: Bug located, not guessed.
함정
- Breakpoints by symbol can match multiple methods in Go interfaces — Breakpoints by symbol can match multiple methods in Go interfaces — qualify with the package path.