Name: dkR10014 Date: 11/25/2002



------------------------------------------------------------------------------
Test : XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt006
Test Base : testbase_nsk
Debuggee VM : Server java_g, Client java_g
Debuggee mode : comp, mixed
Platform (s) : x86
OS : Windows NT 4.0
JDK : 1.4.2-b07, 1.4.1-b21
------------------------------------------------------------------------------

An assertion failure is intermittent and is observed on Windows only when debugged VM
runs with java_g command. The test passes when debugged VM runs with java command.

debugee.stdout> #
debugee.stdout> # HotSpot Virtual Machine Error, assertion failure
debugee.stdout> # Please report this error at
debugee.stdout> # http://java.sun.com/cgi-bin/bugreport.cgi
debugee.stdout> #
debugee.stdout> # Java VM: Java HotSpot(TM) Server VM (1.4.2-beta-b07-debug mixed mode)
debugee.stdout> #
debugee.stdout> # assert(_interp_only_mode >= 0, "enable/disable_interp_only_mode
mismatch")
debugee.stdout> #
debugee.stdout> # Error happened during: change field watch
debugee.stdout> #
debugee.stdout> # Error ID: D:/BUILD_AREA/jdk1.4.2/hotspot\src\share\vm\prims\jvmdi.cpp,
1882
debugee.stdout> #
debugee.stdout> # Thread requesting VM operation: prio=5 tid=0x00780e78 nid=0xbd waiting
on condition
debugee.stdout> #
debugee.stdout>
debugee.stdout> Heap at VM Abort:
debugee.stdout> Heap
debugee.stdout> def new generation total 576K, used 324K [0x10270000, 0x10310000,
0x10980000)
debugee.stdout> eden space 512K, 63% used [0x10270000, 0x102c1368, 0x102f0000)
debugee.stdout> from space 64K, 0% used [0x102f0000, 0x102f0000, 0x10300000)
debugee.stdout> to space 64K, 0% used [0x10300000, 0x10300000, 0x10310000)
debugee.stdout> tenured generation total 1408K, used 0K [0x10980000, 0x10ae0000,
0x14270000)
debugee.stdout> the space 1408K, 0% used [0x10980000, 0x10980000, 0x10980200,
0x10ae0000)
debugee.stdout> compacting perm gen total 16384K, used 1125K [0x14270000, 0x15270000,
0x18270000)
debugee.stdout> the space 16384K, 6% used [0x14270000, 0x143897a0, 0x14389800,
0x15270000)
debugee.stdout> VM option '-ShowMessageBoxOnError'

How to reproduce:
 1. cd /net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/<BugID>
 2. sh doit.sh $JAVA_HOME $ITERATIONS VM_OPTIONS

    where JAVA_HOME must be path to Java SDK,
          ITERATIONS must have positive integer value,
          VM_OPTIONS are optional parameters for debuggee VM.

======================================================================

###@###.### 2003-04-22

I observed this assertion failure during NSK testing for my Forte fixes
on my Solaris 8 SPARC machine running Mantis-B19. My SPARC test machine
for this run was a dual-450MHz Ultra-80.

###@###.### 2003-07-31

This bug also affects the following NSK tests (from 4816644):

    XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt002

During my baseline Mantis-B28 test with the Server VM, I ran into
this assertion failure on Win32 with java_g -Xmixed:

    XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt005

###@###.### 2003-09-09

With the advent of JVM/TI in Tiger, I believe this failure has changed
assertion messages. I saw the following failure with filter_rt002 while
testing the Tiger-B15 snapshot VM:

# Internal Error (/work/build/oliver/1.5.0-baseline-stress/src_ws/src/share/vm/
prims/jvmtiThreadState.cpp, 165 [ Patched ]), pid=10821, tid=15
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0-baseline-stress-fastdebug-debug mix
ed mode)
#
# Error: assert(is_interp_only_mode(),"incr_cur_stack_depth only valid when is_i
nterp_only_mode() is true")


###@###.### 2003-09-10

The following NSK test failed with the "incr_cur_stack_depth only valid
when is_interp_only_mode() is true" failure during my baseline NSK
testing with Tiger-B15 snapshot:

    XXX/jdi/WatchpointRequest/addClassExclusionFilter/filter001


###@###.### 2003-09-24

The following NSK test failed the assertion with my Tiger-B20-snapshot
jvmg Client VM dropped into a Tiger-B19 JDK:

    nsk/jdi/BScenarios/multithrd/tc01x001


###@###.### 2003-10-01

The following tests hit the assertion due to a test bug:

    XXX/jdi/WatchpointRequest/addClassExclusionFilter/filter001
    XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt002
    XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt005
    XXX/jdi/WatchpointRequest/addClassFilter_rt/filter_rt006

Those failures are being tracked by:

    4930911 4/4 TEST_BUG: filter_rt006 debuggee has a race

I replaced the leading 'nsk' in the pathnames with 'XXX' to prevent the
test from showing up on the knownbugs list.