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.

Sign up for GitHub

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

Upgrade to gperftools 2.5 breaks start_profiler() #13

Closed
3 tasks done
krlmlr opened this issue Jul 2, 2017 · 1 comment
Closed
3 tasks done

Upgrade to gperftools 2.5 breaks start_profiler() #13

krlmlr opened this issue Jul 2, 2017 · 1 comment

Comments

@krlmlr
Copy link
Member

krlmlr commented Jul 2, 2017 •
edited
Loading

Ubuntu 16.10 comes with gperftools 2.4, 17.04 has 2.5. Solved locally by manually downloading debs from https://launchpad.net/ubuntu/+source/google-perftools and installing via dpkg -i. Need to figure out the reason, though:

  • compile gperftools 2.4 and 2.5 (at least)
  • run against compiled versions
  • bisect
@krlmlr krlmlr mentioned this issue Dec 7, 2017
Closed
@krlmlr
Copy link
Member Author

krlmlr commented Dec 7, 2017

It seems that gperftools >= 2.5 installs a signal handler once when the library is loaded, while gperftools <= 2.4 install a signal handler when the profiler is started, and remove it afterwards.

@krlmlr krlmlr closed this as completed in a673cb9 Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@krlmlr