-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: Parse: crash in fixInitStmt #72026
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
Comments
Change https://go.dev/cl/653596 mentions this issue: |
Change https://go.dev/cl/654336 mentions this issue: |
Through reverse engineering, I was able to reproduce the overflow of golang/go#72026, and verify the fix of CL 653596. Along the way, I incidentally reproduced golang/go#66766, which I think we can safely ignore now that we understand it. Updates golang/go#72026 Fixes golang/go#66766 Change-Id: I2131d771c13688c1ad47f6bc6285e524fb4c04a1 Reviewed-on: https://go-review.googlesource.com/c/tools/+/654336 Reviewed-by: Alan Donovan <adonovan@google.com> Auto-Submit: Robert Findley <rfindley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This stack
|
This stack
|
This stack
|
This stack
|
This stack
|
This stack
|
Issue created by stacks.
This is not how to use safetoken:
This stack
LKUsng
was reported by telemetry:crash/crash
runtime.gopanic:+69
runtime.goPanicSliceAcap:+2
golang.org/x/tools/gopls/internal/cache/parsego.fixInitStmt:+10
golang.org/x/tools/gopls/internal/cache/parsego.fixAST.func1:+27
golang.org/x/tools/gopls/internal/cache/parsego.walkASTWithParent.func1:+17
go/ast.inspector.Visit:+1
go/ast.Walk:+1
go/ast.Walk:+224
go/ast.walkList[...]:=21
go/ast.Walk:+178
go/ast.Walk:+239
go/ast.walkList[...]:=21
go/ast.Walk:+178
go/ast.Walk:+299
go/ast.walkList[...]:=21
go/ast.Walk:+308
go/ast.Inspect:=372
golang.org/x/tools/gopls/internal/cache/parsego.walkASTWithParent:+2
golang.org/x/tools/gopls/internal/cache/parsego.fixAST:+2
golang.org/x/tools/gopls/internal/cache/parsego.Parse:+57
Dups: Dyo-dQ Cys7zA hq9Myg 7jyMQQ sM9gIg _GxDgw
The text was updated successfully, but these errors were encountered: