-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8326236: assert(ce != nullptr) failed in Continuation::continuation_bottom_sender #23017
Conversation
👋 Welcome back pchilanomate! A progress list of the required criteria for merging this PR into |
@pchilano 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 122 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. ➡️ To integrate this PR with the above commit message to the |
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.
Based on the analysis this seems quite reasonable.
Thanks
Thanks for the reviews David and Markus! |
Going to push as commit ec2aaaa.
Your commit was automatically rebased without conflicts. |
Please review the following fix. In method frame::safe_for_sender() we could read a sender_pc that matches StubRoutines::cont_returnBarrier() but there is no actual continuation in the stack. I added more details in the bug comments on how we can get into this situation. The extra check verifies there is a ContinuationEntry further up in the stack. I run the patch through mach5 tiers 1-2 for sanity testing and tiers 6-7.
Thanks,
Patricio
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23017/head:pull/23017
$ git checkout pull/23017
Update a local copy of the PR:
$ git checkout pull/23017
$ git pull https://git.openjdk.org/jdk.git pull/23017/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23017
View PR using the GUI difftool:
$ git pr show -t 23017
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23017.diff
Using Webrev
Link to Webrev Comment