>>>>> Chris LeDantec writes:
Chris> The problem came in response to a request by one or our
Chris> developers. He is running javadoc against our API, and in
Chris> preview 1, everything runs fine, but in preview 2 it dies
Chris> unexpectedly (my initial guess, without looking at the
Chris> specific error messages, is that he needs to adjust the
Chris> heap size).
Yep, the default heap size was changed in pre2.
Chris> Currently I am downloading a fresh version of the jdk (p2),
Chris> but i've found out more details in re-creating my error.
Chris> If i try to execute the java shell script from the bin dir
Chris> (./java) it returns the problem of not finding
Chris> libjava.so.
That message comes from the wrapper script, it fails to figure out
where the JDK is installed.
Chris> If I execute java from the top level jdk
Chris> directory (./bin/java) I get the a different error (pasted
Chris> at the bottom of this message). This all occurs on a RH
Chris> 6.0 system with a minimal install set (it is used as a
Chris> server, so many of the packages are not installed in the
Chris> interest of saving space).
Chris> I'm using the glibc2.1 jdk on a SuSE machine (my desktop),
Chris> and if I run ./java I get the *same* libjava.so error, but
Chris> if I run ./bin/java everything works.
Chris> *** panic: GC: getStickySystemClass failed: java/lang/ref/Reference
Chris> CLASSPATH may be incorrect
Chris> SIGABRT 6* abort (generated by abort(3) routine)
Chris> stackpointer=0xbffff660
That's the usual result of trying to run a glibc-2.0-JDK on a
glibc-2.1 system. A malloc deep inside libpthread.so fails and the
JDK shows this irritating message.
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Porting Team
http://www.blackdown.org/java-linux.html
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
