| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8226001 | 14 | Serguei Spitsyn | P4 | Resolved | Fixed | team |
The JVMTI spec says the following for PopFrame:
"The specified thread must be suspended (which implies it cannot be the current thread)."
This does not match the implementation. We have several tests that call PopFrame from
an event handler on the current thread and it works.
In opposite, the JVMTI spec correctly says the following for ForceEarlyReturn:
"The specified thread must be suspended or must be the current thread."
The JVMTI spec for PopFrame should be updated to match the wording used with ForceEarlyReturn.
For all the details, please see the related CSR.
"The specified thread must be suspended (which implies it cannot be the current thread)."
This does not match the implementation. We have several tests that call PopFrame from
an event handler on the current thread and it works.
In opposite, the JVMTI spec correctly says the following for ForceEarlyReturn:
"The specified thread must be suspended or must be the current thread."
The JVMTI spec for PopFrame should be updated to match the wording used with ForceEarlyReturn.
For all the details, please see the related CSR.
- backported by
-
JDK-8226001 JVMTI spec incorrectly states that PopFrame cannot be called on the current thread
-
- Resolved
-
- csr for
-
JDK-8225142 JVMTI spec incorrectly states that PopFrame cannot be called on the current thread
-
- Closed
-