Name: dkR10031 Date: 06/13/2000


The Kestrel Solaris beta HotSpot Client VM fails the test
nsk/jvmpi/events/thrstart002 from testbase_nsk.
The test launches two system threads and checks the data of corresponding
THREAD_START events. The second event intermittently contains the
thread group name "<unknown>" instead of expected "system".
Maybe, this error is not too serious since thread group name in this case
is not specified by the spec. Nontheless, I think this is not correct
behavior when the thread's group may differ from time to time.

I could not reproduce this on winNT (1.3.0fcs-C).

To reproduce the bug run
doit.sh <jdk root directory>
in
/net/sqesvr/vsn/GammaBase/Bugs/<this bug number>
The bug shows in both product and debug modes. However this happens not
every time. It is more easy to reproduce it when runnig VM in debug
mode, that is why doit.sh runs java_g.

The test produces the output:

$ doit.sh /export/ld24/java/hotspot/Solaris_JDK_1.3
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-beta)
Java HotSpot(TM) Client VM (build 1.3-beta-debug, mixed mode)
THREAD_START: thr0 system <unknown> -201132592 855784
THREAD_START: thr1 <unknown> <unknown> -201132360 857648
Thread 1: group name expected: system, got: <unknown>

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