-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
1.4.0, 1.4.2
-
generic
-
generic
Testcase :
nsk/jdi/ThreadReference/isSuspended/issuspended002
Failing on all platforms.
LOG:
/net/alpheridies.sfbay/export/VM/merlin/merlin-nightly/DTF-workspace/exec1/NIGHTLY-Serv_Baseline-ClientVM-JDI_FULLLOOK-comp-Solsparc-starwars-2002-01-23-PM-20-36-38-0665/jdk/solsparc/bin/java -client -Xcomp nsk.jdi.ThreadReference.isSuspended.issuspended002 -arch=sparc -waittime=2 -debugee.vmkind=java "-debugee.vmkeys=-client -client -Xcomp"
##Exit status of execution step=97
##!checkExitCode
## ERROR: ##> debugger: ERROR: timeout for waiting for a BreakpintEvent
## ERROR: TEST FAILED
Name: dkR10014 Date: 01/29/2002
The test fails only when debuggee class (issuspended002a class) is running
on Client VM in -Xcomp mode. The test passes in other modes including when
debuggee is running on Server VM in -Xcomp mode.
The failure is observed on Solaris sparc 5.7, Solaris x86 5.8,
Linux RedHat 6.2, Windows NT 4.0.
The test checks that results of the method
com.sun.jdi.ThreadReference.isSuspended()
complies with its spec.
The test checks a case when new thread (thread2) beside main one is created
in debuggee and if thread2.isSuspended() is correct for various suspend
count.
Please see detailed description of test case algorithm in header comment
of issuspended002.java file.
The test fails because the expected Breakpoint event is not received in
debugger. This event should be reported for Breakpoint request been set up
for line in method exclusively invoked in thread2 after resuming.
Below is part of test log demonstrating the failure:
--> debugger: double resuming thread2 with thread2.resume();
--> debugger: thread2.suspendCount() == 1
--> debugger: : thread2.isSuspended()
--> debugger: enabling breakpRequest1
--> debugger: thread2.suspendCount() == 0
--> debugger: : !thread2.isAtBreakpoint() before call to breakpoint()
--> debugger: waiting for BreakpointEvent
--> debugger: new: eventSet = eventQueue.remove();
--> debugger: : eventSet != null; size == 1
--> debugger: VMStartEvent removed
--> debugger: new: eventSet = eventQueue.remove();
# ERROR: ##> debugger: ERROR: timeout for waiting for a BreakpintEvent
--> debugger: resuming both second and main thread
debugee.stderr> **> thread2: entered into block: synchronized (lockingObject)
debugee.stderr> **> thread2: exited from block: synchronized (lockingObject)
debugee.stderr> **> thread2: call to the method 'runt1'
debugee.stderr> **> thread2: method 'runt1' enter
--> debugger: the end of testing
To reproduce bug run script in
/net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/4628004 directory:
sh doit.sh <JAVA_HOME> -client -Xcomp
where "-client -Xcomp" are optional parameters for debuggee VM mode.
======================================================================
nsk/jdi/ThreadReference/isSuspended/issuspended002
Failing on all platforms.
LOG:
/net/alpheridies.sfbay/export/VM/merlin/merlin-nightly/DTF-workspace/exec1/NIGHTLY-Serv_Baseline-ClientVM-JDI_FULLLOOK-comp-Solsparc-starwars-2002-01-23-PM-20-36-38-0665/jdk/solsparc/bin/java -client -Xcomp nsk.jdi.ThreadReference.isSuspended.issuspended002 -arch=sparc -waittime=2 -debugee.vmkind=java "-debugee.vmkeys=-client -client -Xcomp"
##Exit status of execution step=97
##!checkExitCode
## ERROR: ##> debugger: ERROR: timeout for waiting for a BreakpintEvent
## ERROR: TEST FAILED
Name: dkR10014 Date: 01/29/2002
The test fails only when debuggee class (issuspended002a class) is running
on Client VM in -Xcomp mode. The test passes in other modes including when
debuggee is running on Server VM in -Xcomp mode.
The failure is observed on Solaris sparc 5.7, Solaris x86 5.8,
Linux RedHat 6.2, Windows NT 4.0.
The test checks that results of the method
com.sun.jdi.ThreadReference.isSuspended()
complies with its spec.
The test checks a case when new thread (thread2) beside main one is created
in debuggee and if thread2.isSuspended() is correct for various suspend
count.
Please see detailed description of test case algorithm in header comment
of issuspended002.java file.
The test fails because the expected Breakpoint event is not received in
debugger. This event should be reported for Breakpoint request been set up
for line in method exclusively invoked in thread2 after resuming.
Below is part of test log demonstrating the failure:
--> debugger: double resuming thread2 with thread2.resume();
--> debugger: thread2.suspendCount() == 1
--> debugger: : thread2.isSuspended()
--> debugger: enabling breakpRequest1
--> debugger: thread2.suspendCount() == 0
--> debugger: : !thread2.isAtBreakpoint() before call to breakpoint()
--> debugger: waiting for BreakpointEvent
--> debugger: new: eventSet = eventQueue.remove();
--> debugger: : eventSet != null; size == 1
--> debugger: VMStartEvent removed
--> debugger: new: eventSet = eventQueue.remove();
# ERROR: ##> debugger: ERROR: timeout for waiting for a BreakpintEvent
--> debugger: resuming both second and main thread
debugee.stderr> **> thread2: entered into block: synchronized (lockingObject)
debugee.stderr> **> thread2: exited from block: synchronized (lockingObject)
debugee.stderr> **> thread2: call to the method 'runt1'
debugee.stderr> **> thread2: method 'runt1' enter
--> debugger: the end of testing
To reproduce bug run script in
/net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/4628004 directory:
sh doit.sh <JAVA_HOME> -client -Xcomp
where "-client -Xcomp" are optional parameters for debuggee VM mode.
======================================================================
- relates to
-
JDK-4628003 JDI testcase filter_rt001 failing
-
- Resolved
-
-
JDK-4529296 issuspended002 times out waiting for a bkpt with -Xcomp
-
- Closed
-
-
JDK-4627997 JDI testcase crexreq001 failing with -client -Xcomp only, all platforms
-
- Closed
-