Initial support of unattended mode #430
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change allows running BTrace probes in unattended mode when they are not connected to the initiating client.
Having the possibility of running probes in unattended mode comes very handy especially with the recent addition of JFR event support where one can setup a probe to emit custom JFR events and disconnect and leave the application running with the probe applied.
In order to support the unattended execution this PR is adding:
btrace -x <options> <pid> <probe>
)btrace -lp <pid>
)btrace -r <probe id> <pid>
) where probe id is assigned (and displayed) when the probe is first time deployedFor disconnected probes there is small message buffers which can hold up to 5000 most recent messages so when reconnecting one can get the most recent history replayed.