go
runtime_error
ai_generated
true
panic: runtime error: 无效内存地址或 nil 指针解引用 [信号 SIGSEGV]
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x...]
ID: go/panic-runtime-error-invalid-memory-address-or-nil-pointer-
80%修复率
88%置信度
0证据数
2024-10-04首次发现
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| 1.18 | active | — | — | — |
| 1.21 | active | — | — | — |
| 1.22 | active | — | — | — |
根因分析
某个 goroutine 解引用了 nil 指针,通常是 goroutine 启动前未初始化的结构体字段或接口。
English
A goroutine dereferences a nil pointer, often a struct field or interface that was never initialized before the goroutine started.
解决方案
-
92% 成功率
Initialize all shared pointers before launching goroutines, and capture them as arguments: go worker(cfg) where cfg is non-nil.
-
85% 成功率
Add explicit nil checks at goroutine entry: if cfg == nil { log.Fatal("cfg is nil") }.
无效尝试
常见但无效的做法:
-
90% 失败
Recover in main does not catch panics in other goroutines; each goroutine needs its own recover, and hiding the panic masks the bug.
-
75% 失败
Creates a zero-valued object disconnected from the shared state the caller expected, causing silent logic errors.