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.