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

[TESTBUG] serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java failed with JVMTI_ERROR_INVALID_SLOT

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 16
    • 16
    • hotspot
    • b17
    • x86_64
    • linux

      The following test failed in the JDK16 CI:

      serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java

      Here's a snippet from the log file:

      ### Java-Test: 2679 ms Iteration : 128 waitTime : 16
      ### Java-Test: 2725 ms Iteration : 130 waitTime : 32
      AGENT: calling GetLocalObject()
      AGENT: GetLocalObject() result code JVMTI_ERROR_NO_MORE_FRAMES (31)
      ### Java-Test: 2726 ms Iteration : 132 waitTime : 64
      AGENT: calling GetLocalObject()
      AGENT: GetLocalObject() result code JVMTI_ERROR_NONE (0)
      ### Java-Test: 2769 ms Iteration : 134 waitTime : 128
      AGENT: calling GetLocalObject()
      AGENT: GetLocalObject() result code JVMTI_ERROR_NONE (0)
      AGENT: calling GetLocalObject()
      AGENT: GetLocalObject() result code JVMTI_ERROR_NO_MORE_FRAMES (31)
      ### Java-Test: 2846 ms Iteration : 136 waitTime : 256
      AGENT: calling GetLocalObject()
      AGENT: GetLocalObject() result code JVMTI_ERROR_INVALID_SLOT (35)
      FATAL ERROR in native method: AgentThreadLoop: error in JVMTI GetLocalObject

      ----------System.err:(1/85)----------
      AGENT: AgentThreadLoop: error in JVMTI GetLocalObject: JVMTI_ERROR_INVALID_SLOT (35)
      ----------rerun:(43/8590)*----------

        1. UseNewCode_diagnostic_code.patch
          6 kB
          Richard Reingruber
        2. UseNewCode_print_all_vframes_AOT.txt
          21 kB
          Richard Reingruber
        3. UseNewCode_print_all_vframes_WITHOUT_AOT.txt
          27 kB
          Richard Reingruber

            rrich Richard Reingruber
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: