-
Notifications
You must be signed in to change notification settings - Fork 19
8279664: riscv: JFR crashes at 0x0 #49
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
Conversation
👋 Welcome back xlinzheng! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhengxiaolinX Nice catch. In fact, we fixed a similar bug before, and unfortunately missed here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch. This aligns with function "enter()" which creates stack frames. Looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see JFR works quite stable with some non-trivial benchmark workload. So good to go. Thanks.
@zhengxiaolinX This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 16 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@yadongw, @RealFYang) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks for the fast reviews, team! /integrate |
/sponsor |
@zhengxiaolinX |
Going to push as commit 29384f9.
Your commit was automatically rebased without conflicts. |
@RealFYang @zhengxiaolinX Pushed as commit 29384f9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi team,
This is a preview fix for the JFR-related crash - maybe the comment in this patch should be polished.
TIL that complex problems often result from seemingly negligible changes :-)
I need to cautiously test this change, though it seems no harm, to guarantee that it is safe and to ensure the problem is gone so please stay a little tuned.
Update:
test/hotspot/jtreg
on the board reveals no error until now - still testing, but I think it is safe.Thanks,
Xiaolin
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/riscv-port pull/49/head:pull/49
$ git checkout pull/49
Update a local copy of the PR:
$ git checkout pull/49
$ git pull https://git.openjdk.java.net/riscv-port pull/49/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 49
View PR using the GUI difftool:
$ git pr show -t 49
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/riscv-port/pull/49.diff