allan.jacobs@Eng 1997-05-05
Most of the JCK-111a rmi testing is broken JITed on Windows NT.
The problem can be made to occur outside of the JavaTest harness.
The example in the Description section is api/java_rmi/Naming/bind.html#Bind0001.


On a Windows NT 4.0 system with the JIT groups' JDK dated May 2, 1997.
G: maps to a disk containing JCK-111a. F: maps to a directory containing
my workspace. The current working directory is
F:\ajacobs\JCK-111a\intel-NT40\native\unjit\classes

x86-sirius> set CLASSPATH .;C:\java\classes;G:\JCK-111a\classes
x86-sirius> C:\java\bin\javac -J-Djava.compiler=none -nowarn
    -d F:\ajacobs\JCK-111a\intel-NT40\native\unjit\classes
    G:\JCK-111a\tests\api\java_rmi\Naming\BindTests.java
x86-sirius> echo %errorlevel%
0
x86-sirius> set JAVA_COMPILER=none
x86-sirius> C:\java\bin\rmic
   -d F:\ajacobs\JCK-111a\intel-NT40\native\unjit\classes
   javasoft.sqe.tests.api.java.rmi.Naming.NBindImpl
x86-sirius> echo %errorlevel%
0
x86-sirius> C:\java\bin\java -mx32m -verify -Djava.compiler=none
   javasoft.sqe.tests.api.java.rmi.Naming.BindTests -TestCaseID Bind0001
Bind OKAY
x86-sirius> echo %errorlevel%
0
x86-sirius> set JAVA_COMPILER=sunwjit
x86-sirius> C:\java\bin\rmic
   -d F:\ajacobs\JCK-111a\intel-NT40\native\unjit\classes
   javasoft.sqe.tests.api.java.rmi.Naming.NBindImpl

This brings up an Application Error dialog that says "The instruction at
0x77f7d2f3 referenced memory at 0x68dc75ff. The memory could not be written."

x86-sirius> echo %errorlevel%
-1073741819