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/tools/cmd/goimports: panic on usage #39862
Labels
Milestone
Comments
gopherbot
added
the
Tools
This label describes issues relating to any tools in the x/tools repository.
label
Jun 25, 2020
I believe this was introduced by this PR: golang/tools@e31c80b#diff-5e717961381d0f3730aa5f9ee4e11ebc
|
I'm experiencing the same problem |
go get golang.org/x/tools/cmd/goimports
go: finding golang.org/x/tools latest
goimports -w .
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x11cda35]
goroutine 1 [running]:
flag.newStringValue(...)
/usr/local/Cellar/go/1.13/libexec/src/flag/flag.go:226
flag.StringVar(...)
/usr/local/Cellar/go/1.13/libexec/src/flag/flag.go:757
main.init.0()
/Users/me/Server/Go/pkg/mod/golang.org/x/tools@v0.0.0-20200625173320-e31c80b82c03/cmd/goimports/goimports.go:51 +0x85
make: *** [style] Error 2 |
Here's a PR that fixes the issue: golang/tools#239 |
the same problem |
+1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Not related.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go get -u golang.org/x/tools/cmd/goimports
goimports
What did you expect to see?
Not a panic.
What did you see instead?
The text was updated successfully, but these errors were encountered: