-
Notifications
You must be signed in to change notification settings - Fork 3
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
Expose Cachegrind start/stop instrumentation requests #1
Conversation
|
Thank you for pointing this out, i think it's better to stick to "conventional" two-letter tool prefixes to avoid confusion, so :
|
|
Do you want me to change the base of this PR to |
|
Change the prefix from |
|
Ok, done :) |
|
Thank you! |
|
Sure, go ahead :) |
|
available in |
|
Thanks for updating the docs! |
@nnethercote is now in the process of adding client requests to Cachegrind. This PR exposes these requests from crabgrind.
Cachegrind normally uses the
cg_prefix, but I noticed that incrabgrindit's already "reserved" by Callgrind (which usually usescl_. So I usedcag_in this PR to differentiate Callgrind and Cachegrind.