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

x/tools/cmd/guru: Callers seem broken in Go 1.11.2 #28853

Closed
dongfengkuayue opened this issue Nov 18, 2018 · 3 comments
Closed

x/tools/cmd/guru: Callers seem broken in Go 1.11.2 #28853

dongfengkuayue opened this issue Nov 18, 2018 · 3 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@dongfengkuayue
Copy link

dongfengkuayue commented Nov 18, 2018

What version of Go are you using (go version)?

$ go version
1.11.2

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/usernameLibrary/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/username/go/src"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.11.2/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.11.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/username/go/src/xxx/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7m/cnr_fyw56jnf9rvr65jhnbnh0000gn/T/go-build227458918=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I typed :GoCallers in vim ,it reported "vim-go: guru: couldn't load packages due to errors: runtime/internal/sys, runtime, runtime/internal/atomic and 1 more".

What did you expect to see?

the callers of a function.

What did you see instead?

vim-go: guru: couldn't load packages due to errors: runtime/internal/sys, runtime, runtime/internal/atomic and 1 more

and it seemed to have parsing packages in $GOPATH/pkg/mod/...

@dongfengkuayue dongfengkuayue changed the title Go Guru is broken (Go 1.11.2) Go Guru callers is broken (Go 1.11.2) Nov 18, 2018
@odeke-em odeke-em changed the title Go Guru callers is broken (Go 1.11.2) x/tools/cmd/guru: Callers seem broken in Go 1.11.2 Nov 18, 2018
@gopherbot gopherbot added this to the Unreleased milestone Nov 18, 2018
@odeke-em
Copy link
Member

Thank you for filing this bug @dongfengkuayue!

It would be nice to see perhaps the whole error mentioned in

What did you see instead?
vim-go: guru: couldn't load packages due to errors: runtime/internal/sys, runtime, runtime/internal/atomic and 1 more

Kindly paging @alandonovan

@odeke-em odeke-em added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Nov 18, 2018
@agnivade
Copy link
Contributor

@dongfengkuayue - Could you mention the exact steps to get the error without vim-go being involved ? It would be great if you can upload a sample repo or show us a file which throws an error which guru is executed on it. Thanks.

@agnivade agnivade added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Feb 26, 2019
@gopherbot
Copy link

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.)

@golang golang locked and limited conversation to collaborators Mar 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

4 participants