-
Notifications
You must be signed in to change notification settings - Fork 444
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
A new trigger type for global control #1896
Labels
Comments
This is related to #1699. |
Actually we can use For the first case above, this would do the job (but much more verbose).
|
This could be
|
How about the following interface as mentioned at #1699? # trace target program since 10s elapsed from the beginning.
$ uftrace --trace=10s~ ./prog This can be much simpler. |
Yep, that looks better. I think we also need data size support (maybe only needed for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I remember there were some suggestions using file size or elapsed time as a trigger point and associate (global) actions to it (But I cannot find where). For example, we might do things like:
There's
--signal
option for the similar purpose, but it only handles signals. Maybe we can add time and size support there, or have a new option to handle it separately.The text was updated successfully, but these errors were encountered: