-
Notifications
You must be signed in to change notification settings - Fork 554
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
drmemtrace -trace_after_instrs introduces gap between first and second timestamps #6745
Labels
Comments
abhinav92003
added a commit
that referenced
this issue
Mar 29, 2024
Fixes a timestamp gap between the first and second timestamps in the trace caused when -trace_after_instrs is used. Fixes: #6745
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When drmemtrace tracing is done with -trace_after_instrs enabled, the timestamp in the trace buffer at thread-init is set to the then timestamp, but trace entries start pouring in only after the specified count of instrs have passed. This introduces a gap in the first and second timestamp in the trace, which is directly proportional to the requested -trace_after_instrs value.
For a
simple_app
trace collected using:grepping for timestamps in the view tool output shows the diff.
The text was updated successfully, but these errors were encountered: