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

Jump to bottom

runtime: frames for functions called via reflection are not shown in heap profiles #18077

Closed
aalexand opened this issue Nov 28, 2016 · 2 comments
Closed

runtime: frames for functions called via reflection are not shown in heap profiles #18077

aalexand opened this issue Nov 28, 2016 · 2 comments
Labels
FrozenDueToAge
Milestone
Go1.9

Comments

@aalexand
Copy link
Contributor

The issue is filed to discuss google/pprof#54.

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

$ go version
go version go1.7.3 linux/amd64

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

$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/local/google/home/aalexand/go-tools"
GORACE=""
GOROOT="/usr/lib/google-golang"
GOTOOLDIR="/usr/lib/google-golang/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build692899853=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?

See the reproducer in the pprof issue.

What did you expect to see?

Expected the output of pprof to show that the memory is allocated in alloc().

What did you see instead?

The output instead shows that the memory is allocated by reflect.Value.call().

google/pprof#54 (comment) is the proposed fix.
@aalexand aalexand mentioned this issue Nov 28, 2016
Closed
@bradfitz
Copy link
Contributor

/cc @ianlancetaylor

@bradfitz bradfitz changed the title Frames for functions called via reflection are not shown in heap profiles runtime: frames for functions called via reflection are not shown in heap profiles Nov 28, 2016
@bradfitz bradfitz added this to the Go1.9 milestone Nov 28, 2016
@gopherbot
Copy link

CL https://golang.org/cl/33635 mentions this issue.

@golang golang locked and limited conversation to collaborators Nov 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.9
Development

No branches or pull requests
3 participants
@bradfitz @aalexand @gopherbot