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

runtime: in c-archive/c-shared mode, turning on profiling probably won't work #14043

Closed
ianlancetaylor opened this issue Jan 20, 2016 · 1 comment
Milestone

Comments

@ianlancetaylor
Copy link
Contributor

I haven't tested this, but I suspect it is true: if you build a Go library using -buildmode=c-archive or c-shared, and call the Go library from a C program, and the Go library tries to use runtime/pprof.StartCPUProfile, I expect it won't work. The problem is that Go will not have installed the SIGPROF signal handler.

@ianlancetaylor ianlancetaylor self-assigned this Jan 20, 2016
@ianlancetaylor ianlancetaylor added this to the Go1.6 milestone Jan 20, 2016
@gopherbot
Copy link

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

@golang golang locked and limited conversation to collaborators Jan 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants