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

add drcachesim trace markers corresponding to app events or phases #2478

Open
derekbruening opened this issue Jun 19, 2017 · 1 comment
Open

add drcachesim trace markers corresponding to app events or phases #2478

derekbruening opened this issue Jun 19, 2017 · 1 comment

Comments

@derekbruening
Copy link
Contributor

@derekbruening derekbruening commented Jun 19, 2017

For correlating which part of a trace corresponds to which phase of an
application, one approach would be to add annotations to the app using DR's
existing annotation mechanism and having the trace recognize them (and either
mark up the trace or start/stop the trace). If the app cannot be changed, we'd
want to look for certain functions or addresses. This issue covers building
some general support for this type of feature.

@derekbruening

This comment has been minimized.

Copy link
Contributor Author

@derekbruening derekbruening commented Feb 10, 2020

Xref #3995 which is asking for using instruction counts like -trace_after_instrs to delineate multiple app regions: maybe it should be folded into here.

Note that one existing method of doing this is to use the start/stop interface. We have specific tests of this for drcachesim offline traces with static linking: the simplest is here: https://github.com/DynamoRIO/dynamorio/blob/master/clients/drcachesim/tests/burst_static.cpp

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
1 participant
You can’t perform that action at this time.