8367949: JFR: MethodTrace double-counts methods that catch their own exceptions #28947
+360
−30
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.
Could I have a review of a PR that changes how the instrumentation of the MethodTrace and MethodTiming events is implemented, so they handle exceptions in a better way?
For constructors, the current implementation is still used in certain corner cases. A proper implementation would require data-flow analysis, but for all practical purposes this code should work fine.
Testing: jdk/jdk/jfr
Thanks
Erik
Progress
Issue
Reviewers without OpenJDK IDs
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28947/head:pull/28947$ git checkout pull/28947Update a local copy of the PR:
$ git checkout pull/28947$ git pull https://git.openjdk.org/jdk.git pull/28947/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28947View PR using the GUI difftool:
$ git pr show -t 28947Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28947.diff
Using Webrev
Link to Webrev Comment