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/trace: goroutine analysis grouped by PC and reported N=?, but PC is zero and Name is empty #54284

Closed
hitzhangjie opened this issue Aug 5, 2022 · 4 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge

Comments

@hitzhangjie
Copy link
Contributor

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

$ go version
go1.18.3

Does this issue reproduce with the latest release?

I only tried go1.18.3

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

go env Output
$ go env
GO111MODULE="on"
GOARCH="arm64"
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOOS="darwin"
GOVERSION="go1.18.3"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
...

What did you do?

go tool trace trace.out, then view the goroutine analysis, at last there's a N=4, what does it mean?

image

I check the code src/cmd/trace, it is caused by the GDesc.PC / GDesc.Name is zero value.
When does this occasion happend?

What did you expect to see?

I want to know what does it mean, if detailed description is shown, it may be better understood.

What did you see instead?

I see N=4 at last, it is not clear.

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Aug 5, 2022
@hitzhangjie
Copy link
Contributor Author

And, the template cannot render the goroutine func entry (name is empty).

Then, we cannot query by /goroutine?id=0 by click the hyperlink.

@hitzhangjie hitzhangjie changed the title cmd/trace: goroutine analysis grouped by PC and reported N=? at last, but PC is zero and Name is empty cmd/trace: goroutine analysis grouped by PC and reported N=?, but PC is zero and Name is empty Aug 5, 2022
@seankhliao
Copy link
Member

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

@seankhliao seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2022
@hitzhangjie
Copy link
Contributor Author

@seankhliao Yes, I think go tool trace should give a clearer description about which goroutines N=4 is associated.

@hitzhangjie
Copy link
Contributor Author

This is a bug, why just closed it? The final N=4 isn't associated with any goroutine information.

@golang golang locked and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge
Projects
None yet
Development

No branches or pull requests

3 participants