-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
hs16, 5.0
-
generic, x86
-
generic, windows_nt
###@###.### 2003-09-23
I did an NSK run with the Tiger-B20-snapshot VM dropped into a Tiger-B19
JDK and ran into the following test failure:
## ERROR: ##> debugger: ERROR: suspendCounts are not equal for : thread3
## ERROR: ##> debugger: before resuming : 2
## ERROR: ##> debugger: after resuming : 0
I observed this failure in the following NSK test:
nsk/jdi/EventSet/resume/resume001
This failure reproduced on WinNT with java_g -client-test -Xcomp in 1
run out of 20. I have attached the doit.log.7 file.
I observed a similar failure in another resume00 test:
nsk/jdi/EventSet/resume/resume005
Here is a snippet of the .log file:
[2009-08-04T15:05:43.40] --> debugger: ......checking up on EventSet.resume()
[2009-08-04T15:05:43.40] --> debugger: ......--> vm.suspend();
[2009-08-04T15:05:43.40] --> debugger: getting : List all1 = vm.allThreads();
[2009-08-04T15:05:43.40] --> debugger: eventSet.resume;
[2009-08-04T15:05:43.40] --> debugger: getting : List all2 = vm.allThreads();
[2009-08-04T15:05:43.40] --> debugger: getting : int policy = eventSet.suspendPolicy();
[2009-08-04T15:05:43.40] --> debugger: case SUSPEND_NONE
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: ERROR: suspendCounts are not equal for : main
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: before resuming : 1
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: after resuming : 2
[2009-08-04T15:05:43.40] --> debugger: ......--> vm.resume()
[2009-08-04T15:05:43.40] --> debugger: breakpointForCommunication
Here is the java -version info:
java version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b67)
Java HotSpot(TM) Client VM (build 16.0-b07, mixed mode)
The VM was HSX-16-B07 + some of the changes queued up
for HSX-16-B08.
I did an NSK run with the Tiger-B20-snapshot VM dropped into a Tiger-B19
JDK and ran into the following test failure:
## ERROR: ##> debugger: ERROR: suspendCounts are not equal for : thread3
## ERROR: ##> debugger: before resuming : 2
## ERROR: ##> debugger: after resuming : 0
I observed this failure in the following NSK test:
nsk/jdi/EventSet/resume/resume001
This failure reproduced on WinNT with java_g -client-test -Xcomp in 1
run out of 20. I have attached the doit.log.7 file.
I observed a similar failure in another resume00 test:
nsk/jdi/EventSet/resume/resume005
Here is a snippet of the .log file:
[2009-08-04T15:05:43.40] --> debugger: ......checking up on EventSet.resume()
[2009-08-04T15:05:43.40] --> debugger: ......--> vm.suspend();
[2009-08-04T15:05:43.40] --> debugger: getting : List all1 = vm.allThreads();
[2009-08-04T15:05:43.40] --> debugger: eventSet.resume;
[2009-08-04T15:05:43.40] --> debugger: getting : List all2 = vm.allThreads();
[2009-08-04T15:05:43.40] --> debugger: getting : int policy = eventSet.suspendPolicy();
[2009-08-04T15:05:43.40] --> debugger: case SUSPEND_NONE
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: ERROR: suspendCounts are not equal for : main
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: before resuming : 1
[2009-08-04T15:05:43.40] # ERROR: ##> debugger: after resuming : 2
[2009-08-04T15:05:43.40] --> debugger: ......--> vm.resume()
[2009-08-04T15:05:43.40] --> debugger: breakpointForCommunication
Here is the java -version info:
java version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b67)
Java HotSpot(TM) Client VM (build 16.0-b07, mixed mode)
The VM was HSX-16-B07 + some of the changes queued up
for HSX-16-B08.