Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8172969

JVMTI spec: GetCurrentThread may return NULL in the early start phase

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b159
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Not verified

      Backports

        Description

        It was identified in the review of 8172261 that the GetCurrentThread may return NULL during the early start phase. This issue existed with the normal start phase in the initial JVM TI implementation (JDK 1.5).
        Now the GetCurrentThread is Ok to call during the normal start phase as the VMStart event is shifted to the point where the java.base is fully initialized. But now the early VMStart event is at the same point where the VMStart was in all previous releases.
        The JVM TI spec needs an update to say that the GetCurrentThread may return NULL in the early start phase when the java.lang.Thread class has not been initialized yet.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  sspitsyn Serguei Spitsyn
                  Reporter:
                  sspitsyn Serguei Spitsyn
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: