Release Note: JVMTI Specification Clarified when OPAQUE_FRAME Is Thrown for Reasons Other Than a Native Method

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Delivered
    • Priority: P4
    • 26
    • Affects Version/s: 26
    • Component/s: hotspot

      The following JVMTI spec sections have been updated to be made more clear and consistent with regards to which cases the JVMTI_ERROR_OPAQUE_FRAME error code can be returned: PopFrame, NotifyFramePop, ForceEarlyReturn<Type>, GetLocal<Type>, SetLocal<Type>, and the description of the JVMTI_ERROR_OPAQUE_FRAME error code.

            Assignee:
            Serguei Spitsyn
            Reporter:
            Serguei Spitsyn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: