You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
tracing is off by default, and turn it on after 10 seconds
similarly, trace only the first 3 seconds of execution
or trace only from 5 second to 10 second of execution
finish the tracing when file size reaches to 100 MB
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:
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: