nsk.share.Failure: Got unexpected debugee VM exit status: 6 (not 95)

JDK Bug System | Daniel Daugherty | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Bug ID: JDK-6988950 JDWP exit error JVMTI_ERROR_WRONG_PHASE(112)

    java.com | 10 months ago
    nsk.share.Failure: Got unexpected debugee VM exit status: 6 (not 95)
  2. 0

    [JDK-6988950] JDWP exit error JVMTI_ERROR_WRONG_PHASE(112) - Java Bug System

    java.net | 1 year ago
    nsk.share.Failure: Got unexpected debugee VM exit status: 6 (not 95)
  3. 0

    TESTFAIL:demo/jvmti/compiledMethodLoad/CompiledMethodLoadTest.java The following VM/NSK test failed in the 2010.09.30 nightly: nsk/jdi/ReferenceType/isInitialized/isinit003 Here is a snippet from the .log file: [2010-10-01T03:32:01.59] debugger > ReferenceType.isInitialized() returned expected true for type: nsk.jdi.ReferenceType.isInitialized.isinit003Enum8$Enum8_ [2010-10-01T03:32:01.59] debugger > [2010-10-01T03:32:01.59] debugger > Checking completed! [2010-10-01T03:32:01.59] debugee.stderr> debuggee > debugger's <quit> signal received. [2010-10-01T03:32:01.59] debugee.stderr> debuggee > completed succesfully. [2010-10-01T03:32:01.59] debugee.stderr> JDWP exit error JVMTI_ERROR_WRONG_PHASE(112): on checking for an interface [../../../src/share/back/util.c:1311] [2010-10-01T03:32:01.59] debugee.stdout> FATAL ERROR in native method: JDWP on checking for an interface, jvmtiError=JVMTI_ERROR_WRONG_PHASE(112) [2010-10-01T03:32:01.59] debugee.stdout> Current thread is 1091373376 [2010-10-01T03:32:01.59] debugee.stdout> Dumping core ... [2010-10-01T03:32:01.59] # Test level exit status: 1 [2010-10-01T03:32:01.59] Exception in thread "main" nsk.share.Failure: Got unexpected debugee VM exit status: 134 (not 95) [2010-10-01T03:32:01.59] at nsk.share.jdi.Debugee.quit(Debugee.java:496) [2010-10-01T03:32:01.59] at nsk.jdi.ReferenceType.isInitialized.isinit003.run(isinit003.java:77) [2010-10-01T03:32:01.59] at nsk.jdi.ReferenceType.isInitialized.isinit003.main(isinit003.java:48) [2010-10-01T03:32:01.59] # Host info: Linux vm-v20z-21.SFBay.Sun.COM 2.6.18-194.11.1.0.1.el5 #1 SMP Tue Aug 10 17:22:07 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux The following part of the .log file: [2010-10-01T03:32:01.59] debugee.stderr> debuggee > completed succesfully. shows that the debuggee test code reached here in isinit003a.java: pipe.println(isinit003.SIGNAL_READY); receiveSignal(isinit003.SIGNAL_QUIT); => display("completed succesfully."); System.exit(Consts.TEST_PASSED + Consts.JCK_STATUS_BASE); } The following part of the .log file: [2010-10-01T03:32:01.59] Exception in thread "main" nsk.share.Failure: Got unexpected debugee VM exit status: 134 (not 95) [2010-10-01T03:32:01.59] at nsk.share.jdi.Debugee.quit(Debugee.java:496) shows that debugger test code reached here in isinit003.java: execTest(); => debuggee.quit(); return exitStatus; The following VM/NSK test failed with the same JDWP error in the 2010.08.17 nightly: nsk/jdi/ClassLoaderReference/definedClasses/definedclasses005 Here is a snippet of that failure's .log file: [2010-08-18T03:05:02.84] debugger > Checking returned list... [2010-08-18T03:05:02.84] debugee.stderr> debuggee > debuger's <quit> signal reException in thread "main" nsk.share.Failure: Got unexpected debugee VM exit status: 134 (not 95) [2010-08-18T03:05:02.98] at nsk.share.jdi.Debugee.quit(Debugee.java:496) [2010-08-18T03:05:02.98] at nsk.jdi.ClassLoaderReference.definedClasses.definedclasses005.run(definedclasses005.java:82) [2010-08-18T03:05:02.98] at nsk.jdi.ClassLoaderReference.definedClasses.definedclasses005.main(definedclasses005.java:50) [2010-08-18T03:05:02.98] ceived. [2010-08-18T03:05:02.98] debugee.stderr> debuggee > completed succesfully. [2010-08-18T03:05:02.98] debugee.stdout> FATAL ERROR in native method: JDWP on checking for an interface, jvmtiError=JVMTI_ERROR_WRONG_PHASE(112) [2010-08-18T03:05:02.98] debugee.stdout> Current thread is 1083562304 [2010-08-18T03:05:02.98] debugee.stdout> Dumping core ... [2010-08-18T03:05:02.98] debugee.stderr> JDWP exit error JVMTI_ERROR_WRONG_PHASE(112): on checking for an interface [../../../src/share/back/util.c:1311] [2010-08-18T03:05:02.98] # Test level exit status: 1 [2010-08-18T03:05:02.98] # Host info: Linux vm-amd64-05.sfbay.sun.com 2.6.18-164.9.1.el5 #1 SMP Wed Dec 9 03:27:37 EST 2009 x86_64 x86_64 x86_64 GNU/Linux The following VM/NSK JDI test failed in the 2010.10.04 nightly: nsk/jdi/Method/isVarArgs/isvarargs001 The failure mode is similar but not identical to the previous failure modes: [2010-10-05T03:21:47.29] debugee.stderr> JDWP exit error JVMTI_ERROR_WRONG_PHASE(112): signature [../../../src/share/back/eventHelper.c:385] [2010-10-05T03:21:47.29] Exception in thread "main" nsk.share.Failure: Got unexpected debugee VM exit status: 134 (not 95) [2010-10-05T03:21:47.29] at nsk.share.jdi.Debugee.quit(Debugee.java:496) [2010-10-05T03:21:47.29] at nsk.jdi.Method.isVarArgs.isvarargs001.run(isvarargs001.java:73) [2010-10-05T03:21:47.29] at nsk.jdi.Method.isVarArgs.isvarargs001.main(isvarargs001.java:45) [2010-10-05T03:21:47.29] # Test level exit status: 1 [2010-10-05T03:21:47.29] # Host info: Linux vm-amd64-06 2.6.18-194.11.1.0.1.el5 #1 SMP Tue Aug 10 17:22:07 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux Another sighting of a slightly different version of this failure mode in the 2011.04.23 Main_Baseline nightly in the following JT_JDK/demo/jvmti test: demo/jvmti/compiledMethodLoad/CompiledMethodLoadTest.java Here is a snippet from the .jtr file: ----------messages:(3/143)---------- command: main CompiledMethodLoadTest Hello reason: User specified action: run main CompiledMethodLoadTest Hello elapsed time (seconds): 2.953 ----------System.out:(12/791)---------- Starting: /export/local/common/jdk/baseline/linux-i586/jre/bin/java -cp /export/local/48416.JDK7.NIGHTLY.VM+linux-i586_javase_client_mixed_JT_JDK_demo_jvmti/results/workDir/classes/demo/jvmti/compiledMethodLoad -Dtest.classes=/export/local/48416.JDK7.NIGHTLY.VM+linux-i586_javase_client_mixed_JT_JDK_demo_jvmti/results/workDir/classes/demo/jvmti/compiledMethodLoad -Xcheck:jni -Xverify:all -agentpath:/export/local/common/jdk/baseline/linux-i586/jre/../demo/jvmti/compiledMethodLoad/lib/libcompiledMethodLoad.so Hello Hello ERROR: JVMTI: 112(JVMTI_ERROR_WRONG_PHASE): get method declaring class Exit code is 3 <beginning of Error Stream buffer> ERROR: JVMTI: 112(JVMTI_ERROR_WRONG_PHASE): get method declaring class <end of buffer> <beginning of Input Stream buffer> Hello <end of buffer> ----------System.err:(15/913)---------- java.lang.RuntimeException: Test failed - exit return code non-zero (exitStatus==3) at DemoRun.runit(DemoRun.java:216) at DemoRun.runit(DemoRun.java:109) at CompiledMethodLoadTest.main(CompiledMethodLoadTest.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:598) at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94) at java.lang.Thread.run(Thread.java:722) JavaTest Message: Test threw exception: java.lang.RuntimeException: Test failed - exit return code non-zero (exitStatus==3) JavaTest Message: shutting down test STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test failed - exit return code non-zero (exitStatus==3) result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Test failed - exit return code non-zero (exitStatus==3) test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Test failed - exit return code non-zero (exitStatus==3)

    JDK Bug System | 6 years ago | Daniel Daugherty
    nsk.share.Failure: Got unexpected debugee VM exit status: 6 (not 95)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. nsk.share.Failure

      Got unexpected debugee VM exit status: 6 (not 95)

      at nsk.share.jdi.Debugee.quit()
    2. nsk.share.jdi
      Debugee.quit
      1. nsk.share.jdi.Debugee.quit(Debugee.java:534)
      1 frame
    3. nsk.jdi.IntegerValue
      compareto001.main
      1. nsk.jdi.IntegerValue.compareTo.compareto001.run(compareto001.java:77)
      2. nsk.jdi.IntegerValue.compareTo.compareto001.main(compareto001.java:48)
      2 frames