-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8371474: Wrong object class or methodID passed to JNI call in TestSharedCloseJvmti with -Xshare:off #28202
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 jvernee! A progress list of the required criteria for merging this PR into |
|
@JornVernee 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 23 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 |
|
@JornVernee The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
AlanBateman
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.
Yes, using VMInit so the code executes when the VM is fully initialized is right.
TheRealMDoerr
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.
LGTM and fixes the issue. Thanks!
Thanks for the initial investigation! |
|
/integrate |
|
Going to push as commit 6e838d6.
Your commit was automatically rebased without conflicts. |
|
@JornVernee Pushed as commit 6e838d6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The existing test uses the JVMTI
VMStartcallback to look up a class. This works when using CDS, because the class is already available, but becauseVMStartis called while the VM is still being initialized, it fails to find the target class when CDS is turned off.Instead, the
VMInitcallback should be used, which runs after the VM has been initialized. This patch does this. Additionally, it delays the call to allocateOTHER_SEGMENT. If we callFindClassduringVMInit, the<clinit>of the class will run, which then ends up callingcheckValidStateRawas a result of allocatingOTHER_SEGMENT, and we get to our method exit event code before the target class and method ID have been initialized.As a side note: I had know about the difference between
VMInitandVMStart, and had actually intended to useVMInitin the first place, but I seem to have gotten the two confused, because they are listed in reverse chronological order in the list under 'Set Event Notification Mode' in the JVMTI spec (https://docs.oracle.com/en/java/javase/25/docs/specs/jvmti.html#SetEventNotificationMode).Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28202/head:pull/28202$ git checkout pull/28202Update a local copy of the PR:
$ git checkout pull/28202$ git pull https://git.openjdk.org/jdk.git pull/28202/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28202View PR using the GUI difftool:
$ git pr show -t 28202Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28202.diff
Using Webrev
Link to Webrev Comment