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

serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java fails with unexpected exit code: 112

XMLWordPrintable

    • b10

      serviceability/jvmti/StartPhase/AllowedFunctions/AllowedFunctions.java failed, but the test did not handle the failure well. At the end of stdout you see:

      VMInit event
        ## GetCurrentThread error: 112

      This comes from:

      static void check_jvmti_error(jvmtiEnv *jvmti, char* fname, jvmtiError err) {
          if (err != JVMTI_ERROR_NONE) {
              printf(" ## %s error: %d\n", fname, err);
              exit(err);
          }
      }

      So basically if the test gets a JVMTI error, it will call exit() with that error. In this case 112 is JVMTI_ERROR_WRONG_PHASE. However, since no error was reported to JTREG, stderr reports:

      STATUS:Passed.

      But then I guess during JTREG test cleanup, it detects that the process had an exit code but claimed to have passed, so the end of the log contains:

      result: Error. unexpected exit code: 112, doesn't match exit status: "Passed." which was reported by the test process

            sspitsyn Serguei Spitsyn
            cjplummer Chris Plummer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: