I've got a project which I've been working on for several months which
implements a Java GUI for a bunch of C++ DNA mapping algorithms.  After I
upgraded to RH 5.0, I had to go through hell to install a full set of
libc5 development tools because at the time, there were no reliable glibc
JDKs.

  Since then, I have tried some of the new JDK/glibc versions, but for
some reason, my native methods cause the program to crash.  In particular,
I am running Steve Byrne's JDK 1.1.5v6 for libc5, and everything works
fine as long as I link to libc5 when I compile the native methods. 

  Yesterday, I thought I would try once again to use the latest glibc JDK,
1.1.5v7.  I downloaded it, I grabbed the latest update of glibc off the
RedHat site, and recompiled all of my native code, linking it to glibc.
Even under this version, the program still crashes as soon as it tries to
execute a native method, even using java_g (it runs fine up until that
first native call, however). Just as a sanity check, I've run it again
under the libc5 version, and also IBM's JDK 1.1.4 for AIX, which I have
available on another machine.  It works fine under both those conditions. 

  Does anyone have any ideas on how to fix this problem, or if there is
any way I can figure out what is going wrong?  I can keep going with libc5
for now, but I would love to do away with the kludgy setup I need to
compile with libc5 under RH 5.0. 

Dan


Reply via email to