JDK-8153266 : com/sun/jdi/EvalInterfaceStatic.sh fails in the nightlies
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • Submitted: 2016-04-01
  • Updated: 2016-06-15
  • Resolved: 2016-06-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Relates :  
Description
Here is some output:

vv jdbOutFile  vvvvvvvvvvvvvvvvvvvvvvvvvvvv
Listening at address: spb23455.ru.oracle.com:40154
Set uncaught java.lang.Throwable
Set deferred uncaught java.lang.Throwable
Initializing jdb ...
> 
VM Started: No frames on the current call stack

main[1] Deferring breakpoint EvalStaticInterfaces:21.
It will be set after the class is loaded.
main[1] > Set deferred breakpoint EvalStaticInterfaces:21
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- jdb process info ----------------------
      22225 com.sun.tools.example.debug.tty.TTY -Dapplication.home=/scratch/local/aurora/CommonData/TEST_JAVA_HOME -Xms8m -DHANGINGJAVA-22061_JDB -Djdk.module.main=jdk.jdi
-- jdb threads: jstack 22225 com.sun.tools.example.debug.tty.TTY -Dapplication.home=/scratch/local/aurora/CommonData/TEST_JAVA_HOME -Xms8m -DHANGINGJAVA-22061_JDB -Djdk.module.main=jdk.jdi
--waitForFinish: Waiting for mydojdbCmds() to finish
Usage:
    jstack [-l] <pid>
        (to connect to running process)
    jstack -F [-m] [-l] <pid>
        (to connect to a hung process)
    jstack [-m] [-l] <executable> <core>
        (to connect to a core file)
    jstack [-m] [-l] [server_id@]<remote server IP or hostname>
        (to connect to a remote debug server)

Options:
    -F  to force a thread dump. Use when jstack <pid> does not respond (process is hung)
    -m  to print both java and native frames (mixed mode)
    -l  long listing. Prints additional information about locks
    -h or -help to print this help message
------------------------------------------

-- debuggee process info ----------------------
      22310 EvalStaticInterfaces -DHANGINGJAVA-22061_DEB -Xcomp -XX:-TieredCompilation -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -Xcomp -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:+AggressiveOpts -XX:-UseBiasedLocking -Djtreg.classDir=/scratch/local/aurora/sandbox/results/workDir/classes/1/com/sun/jdi/aa22061 -agentlib:jdwp=transport=dt_socket,address=40154,server=n,suspend=y
-- debuggee threads: jstack  22310
22310: Unable to open door: target process not responding or HotSpot VM not loaded
The -F option can be used when the target process is not responding
=============================================

-rw-r--r--   1 root     root         136 Apr  1 06:13 /scratch/local/aurora/sandbox/results/workDir/classes/1/com/sun/jdi/aa22061/testFailed
<waitForFinish:_begin_failFile_contents>
--Fail: waitForJdbMsg timed out after 40 seconds, looking for /[a-zA-Z0-9_-][a-zA-Z0-9_-]*\\[[1-9][0-9]*\\] [ >]*$/, in 1 lines; exitting
<waitForFinish:_end_failFile_contents>
-rw-r--r--   1 root     root         136 Apr  1 06:13 /scratch/local/aurora/sandbox/results/workDir/classes/1/com/sun/jdi/aa22061/testFailed
<cleanup:_begin_failFile_contents>
--Fail: waitForJdbMsg timed out after 40 seconds, looking for /[a-zA-Z0-9_-][a-zA-Z0-9_-]*\\[[1-9][0-9]*\\] [ >]*$/, in 1 lines; exitting
<cleanup:_end_failFile_contents>