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
I am looking for help on how to continue tracking this problem to its
source. A solution would be nice, but it is not expected.
I am using jdk1.5.0_01-x86_64 and have created a C++ library that
creates an embedded JVM. I want to use a bunch of Java that I have
written from within Octave (see www.
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
Hi,
My AWT HelloWorldAwt.java invoked thru C++/JNI is crashing my Linux box!
My first Linux crash after 3 years :-(
It eats up all my memory 128MB + swap 128MB in a few seconds.
The same HelloWorldAwt.java works well with JDK 1.1.x - JNI (C++
invoked)
and invoked with JDK 1.2 Pre2 directly (ja
I have been reporting problems with JNI/Invocation
with JDK 1.1.7v1a+native for apps that use libdl.so,
a bug which has been confirmed by Blackdown.
By accident I discovered a quick patch on this problem
that seems to work fine on my Debian "slink" snapshot,
so if you happen to be stuck with a
