Skip to content
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

cmd/vet: go vet -vettool=$(which shadow) errors in go1.13 only (flag provided but not defined: -unsafeptr) [1.13 backport] #34922

gopherbot opened this issue Oct 15, 2019 · 2 comments


Copy link

@gopherbot gopherbot commented Oct 15, 2019

@bcmills requested issue #34053 to be considered for backport to the next 1.13 minor release.

@gopherbot, please backport to 1.13: this was an early regression and the fix is trivial.

Copy link

@gopherbot gopherbot commented Oct 15, 2019

Change mentions this issue: [release-branch.go1.13] cmd/go/internal/work: fix error while passing custom vet tool

Copy link

@gopherbot gopherbot commented Oct 17, 2019

Closed by merging 0b575b4 to release-branch.go1.13.

@gopherbot gopherbot closed this Oct 17, 2019
gopherbot pushed a commit that referenced this issue Oct 17, 2019
… custom vet tool

For GOROOT packages, we were adding -unsafeptr=false to prevent unsafe.Pointer
checks. But the flag also got passed to invocations of go vet with a custom
vet tool. To prevent this from happening, we add this flag only when no
tools are passed.

Updates #34053
Fixes #34922

Change-Id: I8bcd637fd8ec423d597fcdab2a0ceedd20786019
Run-TryBot: Agniva De Sarker <>
TryBot-Result: Gobot Gobot <>
Reviewed-by: Jay Conrod <>
(cherry picked from commit 902d5aa)
Run-TryBot: Bryan C. Mills <>
Reviewed-by: Agniva De Sarker <>
@golang golang locked and limited conversation to collaborators Oct 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.