#!stacks
"sigpanic" && "metadata.(*Graph).Update:+0"
Issue created by stacks.
These are the only instructions at the indicated line:
TEXT golang.org/x/tools/gopls/internal/cache/metadata.(*Graph).Update(SB) /tmp/stacks-cache/tools/gopls/internal/ca
che/metadata/graph.go
graph.go:40 0x100762910 f9400b90 MOVD 16(R28), R16 <---- SEGV
graph.go:40 0x100762914 d102c3f1 SUB $176, RSP, R17
graph.go:40 0x100762918 eb10023f CMP R16, R17
graph.go:40 0x10076291c 540018e9 BLS 199(PC)
graph.go:40 0x100762920 d104c3f4 SUB $304, RSP, R20
graph.go:40 0x100762924 a93ffa9d STP (R29, R30), -8(R20)
graph.go:40 0x100762928 9100029f MOVD R20, RSP
graph.go:40 0x10076292c d10023fd SUB $8, RSP, R29
Only the initial load (MOVD) or later store (STP) can SEGV, so this indicates either a bad g register, or a g struct with a bad stack pointer.
This stack Lb6hkg
was reported by telemetry:
crash/crash
runtime.throw:+9
runtime.sigpanic:+33
golang.org/x/tools/gopls/internal/cache/metadata.(*Graph).Update:+0
golang.org/x/tools/gopls/internal/cache.(*Snapshot).load:+248
golang.org/x/tools/gopls/internal/cache.(*Snapshot).initialize:+89
golang.org/x/tools/gopls/internal/cache.(*Session).createView.func3:+2
runtime.goexit:+0
golang.org/x/tools/gopls@v0.18.1 go1.23.5 darwin/arm64 other,vscode-insiders (1)
Comment From: gabyhelp
Related Issues
- x/tools/gopls: SEGV in gcimporter.iexportCommon (bad SP) #72135
- x/tools/gopls: SEGV while clearing memory in newobject #71561
- x/tools/gopls: SEGV updating non-nil map in analysis.Validate #73437
- x/tools/gopls: SEGV accessing map[string]... #73387
- x/tools/gopls: impossible SEGV in regexp/syntax.MatchRunePos #73090
- x/tools/gopls: panic in aeshashbody on behalf of mapaccess2_faststr: string memory corrupted #71367
- gopls SEGV fault on startup. #70271 (closed)
- runtime: SEGV in mapaccess2 (go1.23.2 darwin/amd64) #71123
- x/tools/gopls: sigpanic in persistent.(*mapNode).forEach (bad SP) #71115
- x/tools/gopls: spurious SEGV in Promise #73967
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)