ClassLoader initialization in _Jv_RunMain

Fri Nov 14 18:48:00 GMT 2003

Mark Wielaard wrote:
> Hi,
>> On Fri, 2003年11月14日 at 16:07, Andreas Tobler wrote:
>>>Mark Wielaard wrote:

>> That is certainly progress :)
> No more core dumps and/or huge stacktraces indicating bootstrap
> classloader looping. That simple.jar file looks corrupt to me. Running
> fastjar xf simple.jar gives: Error! CRCs do not match! Got fd0659a5,
> expected 2d4740b5
>> So the above output "Failed to load Main-Class manifest attribute" is
> correct.

Aha.
[titanium:gcc-cvs-dylib/objdir/fastjar] andreast% ./jar -xf 
/Volumes/xufs/gcc-cvs-clean/gcc/libjava/testsuite/libjava.jar/simple.jar
Error! CRCs do not match! Got fd0659a5, expected 2d4740b5
And the below with the OS-X java. With the setTime NOT commented.
[titanium:gcc-cvs-dylib/objdir/fastjar] andreast% java -jar 
/Volumes/xufs/gcc-cvs-clean/gcc/libjava/testsuite/libjava.jar/simple.jar
Exception in thread "main" java.io.IOException: invalid manifest format
 at java.util.jar.Manifest.read(Manifest.java:186)
 at java.util.jar.Manifest.<init>(Manifest.java:52)
 at java.util.jar.JarFile.getManifest(JarFile.java:148)
Anyway. There must be an additional error in the testsuite I guess:
These bytecompile errors should not appear.
FAIL: bytecompile 
/Volumes/xufs/gcc-cvs-dylib/gcc/libjava/testsuite/libjava.jni/calls.java
See the gcc-results list for more.
Andreas