-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vuln: panic while running govulncheck with 1.23+ (panic: *types.Alias: any) #70350
Comments
What version of go was govulncheck built with? |
1.23.3 (everything runs in Bazel on with 1.23.3 workspace)
|
Any chance we get a reproducer? Thanks for reporting this! |
trying to find a minimal repro, but the error is not helping a lot. |
The code in the stack trace was removed in https://go.dev/cl/573135. That was Mar 21, 2024. Alias support for 1.23 has improved since then for x/tools/go/ssa and should have fixed this. Aliases were enabled for 1.23+ toolchains in https://go.dev/cl/627715. If you just picked up https://go.dev/cl/627715 , you need to update your copy of x/tools too. |
thanks @timothy-king, to test, I added this in my go.mod: no more panics so far! |
just got one, but could be cache related. Will clean and retry everything from 0 panic: Cannot range over: func(yield func(K, V) bool)
goroutine 78045 [running]:
golang.org/x/tools/go/ssa.(*builder).rangeStmt(0x141a6fb1d20, 0x1406eae8820, 0x14001f8a720, 0x0)
external/org_golang_x_tools/go/ssa/builder.go:2278 +0x690
golang.org/x/tools/go/ssa.(*builder).stmt(0x141a6fb1d20, 0x1406eae8820, {0x104ffd270?, 0x14001f8a720?})
external/org_golang_x_tools/go/ssa/builder.go:2508 +0x1d8
golang.org/x/tools/go/ssa.(*builder).stmtList(...)
external/org_golang_x_tools/go/ssa/builder.go:908
golang.org/x/tools/go/ssa.(*builder).stmt(0x141a6fb1d20, 0x1406eae8820, {0x104ffd150?, 0x1400632af60?})
external/org_golang_x_tools/go/ssa/builder.go:2470 +0xc1c
golang.org/x/tools/go/ssa.(*builder).buildFromSyntax(0x141a6fb1d20, 0x1406eae8820)
external/org_golang_x_tools/go/ssa/builder.go:2582 +0x204
golang.org/x/tools/go/ssa.(*builder).buildFunction(0x104f65601?, 0x1406eae8820)
external/org_golang_x_tools/go/ssa/builder.go:2536 +0x110
golang.org/x/tools/go/ssa.(*builder).iterate(0x141a6fb1d20)
external/org_golang_x_tools/go/ssa/builder.go:2524 +0x2c
golang.org/x/tools/go/ssa.(*Package).build(0x1414184f280)
external/org_golang_x_tools/go/ssa/builder.go:2658 +0xa4
sync.(*Once).doSlow(0xd1?, 0x1408368ee00?)
GOROOT/src/sync/once.go:76 +0xf8
sync.(*Once).Do(...)
GOROOT/src/sync/once.go:67
golang.org/x/tools/go/ssa.(*Package).Build(...)
external/org_golang_x_tools/go/ssa/builder.go:2647
golang.org/x/tools/go/ssa.(*Program).Build.func1(0x0?)
external/org_golang_x_tools/go/ssa/builder.go:2626 +0x50
created by golang.org/x/tools/go/ssa.(*Program).Build in goroutine 73632
external/org_golang_x_tools/go/ssa/builder.go:2625 +0x17c |
Let us know if this cleared up the |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Go version
go version go1.23.3 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
govulncheck -show traces,verbose -C $EXEC_ROOT/{bin_dir}/go/doublezero.io/gopath/src/doublezero.io ./...
tested with govuln 1.1.3 and also latest master. Same behavior.
What did you see happen?
When using go 1.23+
no issues with 1.22.7
What did you expect to see?
no panic, and the output of govulncheck
The text was updated successfully, but these errors were encountered: