One of our regression tests is failing since b23 when -Xcheck:jni
is used.

A minimal hello world app will also show the same symptom
when run with -Xcheck:jni from jtreg.

The test is test/java/net/InetAddress/CheckJNI

The output is:

----------messages:(3/139)----------
command: main -Xcheck:jniCheckJNI
reason: User specified action: run main/othervm -Xcheck:jni CheckJNI
elapsed time (seconds): 10.935
----------System.out:(14/875)----------
FATAL ERROR in native method: Bad global or local ref passed to JNI
at java.lang.ClassLoader.findBootstrapClass(Native Method)
at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:852)
at java.lang.ClassLoader.loadClass(ClassLoader.java:284)
- locked <0x6e183358> (a sun.misc.Launcher$ExtClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
- locked <0x6e18a220> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:279)
- locked <0x6e18a220> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
- locked <0x6e18a220> (a sun.misc.Launcher$AppClassLoader)
at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:75)
at java.lang.Thread.run(Thread.java:549)
----------System.err:(0/0)----------
result: Failed. Unexpected exit from test [exit code: 1]

I notice there were some recent changes to ClassLoader.c around that time.

The problem occurs on Windows only. I tested with Win 2000.

###@###.### 2003-10-30