-
Notifications
You must be signed in to change notification settings - Fork 253
8266889: [macosx-aarch64] Crash with SIGBUS in MarkActivationClosure::do_code_blob during vmTestbase/nsk/jvmti/.../bi04t002 test run #817
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
8262896: [macos_aarch64] Crash in jni_fast_GetLongField
…blob during vmTestbase/nsk/jvmti/.../bi04t002 test run
|
👋 Welcome back vkempik! A progress list of the required criteria for merging this PR into |
|
This backport pull request has now been updated with issue from the original commit. |
AntonKozlov
left a comment
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.
Looks good. It's probably possible to move W^X flip under thread->is_Java_thread() condition, but the current code is safer.
adinn
left a comment
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.
Looks good
|
The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8253795
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@VladimirKempik This change now passes all automated pre-integration checks. 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
|
|
|
/integrate |
|
@VladimirKempik Pushed as commit 69583df. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this backport. Not applying clean. A follow up patch for jep-391 backport
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/817/head:pull/817$ git checkout pull/817Update a local copy of the PR:
$ git checkout pull/817$ git pull https://git.openjdk.java.net/jdk11u-dev pull/817/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 817View PR using the GUI difftool:
$ git pr show -t 817Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/817.diff