Thank you for the help. Using LD_PRELOAD, I was able to change the error
quite a bit. Now it fails after starting the JVM because the current
stack is corrupt. I am not sure if this is an improvement or not, but it
does mean I should be able to try various JVMs. Unfortunately, I have
been building
Al Niessner <[EMAIL PROTECTED]> writes:
> Since it works with a C++ main(), I am guessing that there is some
> symbol in Octave that is clashing with what libzip.so
Probably, AFAIK Sun internalizes symbols in the i386 build but not in
the x86-64 and ia64 builds. Our 1.4.2-01 for x86-64 should be
Hi,
i used a symbolic link to point to the JDK 1.2pre2, this crashed my
whole Linux :
in /usr/local:
drwxr-xr-x 9 marcel users1024 Jun 9 15:03 jdk1.2Pre2
lrwxrwxrwx 1 marcel users 10 Jun 8 21:47 jdk
->jdk1.2Pre2
in conjunction with using:
echo $LD_LIBRARY
