Hi Raj.
I'm guessing that you have glibc-2.1.1 on your box, which is the
version that is shipped with RedHat 6.0, and jdk1.2.2 RC3
needs glibc-2.1.2. JDK1.2pre-v2 needs glibc-2.1.1, which is
why you didn't have any trouble with that.
Hope this helps.
jason
Raj Patel wrote:
> Hi everybody,
>
Hi everybody,
I had some problem with threading using JNI
application and i decided to try newer version of jdk. I downloaded
jdk1.2.2 for i386 rc3 version and file called
jdk-1.2.2-RC3-linux-i386.tar.bz2
After i installed it when i tried to compile and run my applic
Nathan Meyers wrote:
> OK... it's never dumped core there before, has it?
>
> I'm getting a bit short of ideas and time, but let's see if I can make
> any headway. It's dying as soon as you start up "java -green" with my
> two recommended environment variable values (JAVA_DEBUG and LD_PRELOAD)?
>
I don't know about your problem, but I *do* know that you have to set
THREADS_FLAG=green
JAVA_COMPILER=NONE
to get jdb to run.
Thus spake Raj Patel on Fri, 12 Nov 1999:
> Hi,
> I am putting this problem here one more time. I have a swing
> application using
> JNI. Everything was wor
Nathan Meyers wrote:
> There isn't really a gdb-jdb combination. You can debug under gdb if
> you want to debug native code, but you won't get source-level Java
> debugging.
>
> There are some tricks to getting your debugging session started under
> gdb, because the breakpoint needs to be set in
There isn't really a gdb-jdb combination. You can debug under gdb if
you want to debug native code, but you won't get source-level Java
debugging.
There are some tricks to getting your debugging session started under
gdb, because the breakpoint needs to be set in a library (your JNI code)
that is
Nathan Meyers wrote:
> I think you didn't get an answer because, in general, people are
> successfully using Swing and JNI with the JDK1.2 and nobody recognized
> your problem.
Thanks for the response. I found the problem. Now i have some trouble in
native calls. I have Redhat Linux 6.0 with
I think you didn't get an answer because, in general, people are
successfully using Swing and JNI with the JDK1.2 and nobody recognized
your problem.
> I am using Linux6.0(glibc2.0) jdk1.2(blackdown).
> Is there any known problem with this transition??
Yes, there are known problems with the JDK1
Hi,
I am putting this problem here one more time. I have a swing
application using
JNI. Everything was working ok under blackdown jdk 1.1.7 with
swing-1.1.1 . Now
i upgraded jdk to jdk 1.2(blackdown) so i don't have to have swing
because it is
already built in. But now under jdk1.2 my
