Hi, > You might get a more useful test failure if you compile with jikes. > Then, ideally, one of the actual tests will fail (vs. compilation of > the test) and that should help pinpoint the problem.
Guess what? I could manually compile ThreadState.java for example. That is: . ../../BUILD_ENVIRONMENT $JAVA at.dms.kjc.Main ThreadState.java Then running it prints three "success" then segfaults. - Interestingly another test that failed (internal error while compiling) was URLTest. Again, manually compiling it succeeds. Likewise for running it. That's with the "pthreads" implementation. I could manually compile many of those tests that failed to compile at make check. - Case of DoubleComp.java. Even manually compiling it fails with kjc (internal error, java/lang/NullPoinerException caught). However, compiling it with jikes succeeds. The test run succeeds too. Bye, Gwenole _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
