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/go: stop writing pkg.test executable in directory when profiling? #46086

Open
josharian opened this issue May 10, 2021 · 0 comments
Open

cmd/go: stop writing pkg.test executable in directory when profiling? #46086

josharian opened this issue May 10, 2021 · 0 comments

Comments

@josharian
Copy link
Contributor

@josharian josharian commented May 10, 2021

$ go test -bench=. -cpuprofile=cpu.pprof pkg

results in cmd/go writing pkg.test to the current directory. The original reason was so that pkg.test would be handy when running go tool pprof. But go tool pprof no longer requires access to the original executable, because the requisite information is in the profile itself.

Maybe we should stop writing it.

@josharian josharian changed the title cmd/go: stop write pkg.test executable in directory when profiling? cmd/go: stop writing pkg.test executable in directory when profiling? May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants