Skip to content
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

Fix jvmtiGetVirtualThread and make it more robust #16787

Merged
merged 1 commit into from
Mar 1, 2023

Conversation

babsingh
Copy link
Contributor

If no virtual thread is mounted on the targetThread i.e.
carrierThreadObject == threadObject, then return null
for the output virtual thread value.

Virtual thread is not pinned in this function. So, read
threadObject and carrierThreadObject once and store
their values to avoid inconsistency.

Related: #16688
Related: #16751

If no virtual thread is mounted on the targetThread i.e.
carrierThreadObject == threadObject, then return null
for the output virtual thread value.

Virtual thread is not pinned in this function. So, read
threadObject and carrierThreadObject once and store their
values to avoid inconsistency.

Related: eclipse-openj9#16688
Related: eclipse-openj9#16751

Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
@babsingh babsingh marked this pull request as ready for review February 27, 2023 22:03
@gacholio
Copy link
Contributor

gacholio commented Mar 1, 2023

jenkins test sanity zlinux jdk19

@gacholio gacholio merged commit 8078ad6 into eclipse-openj9:master Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants