This is really getting into gdb questions, rather than Java questions.
First, it helps if you use both java_g and be sure to compile your native
library with gcc -g (so you have debugging information). "Renaming" the
library to use the _g suffix isn't the point; such a library is meant to be
com
Hi folks. Thanks to all of you who have responded so far...I've made
excellent progress and am almost there. Here's the scoop...
1. I've made sure the library in question is in the $LD_LIBRARY_PATH, and
has
been renamed to libBlah_g.so... in my case, I'm creating
libTest5Native.so, and renaming i
> Matt Welsh writes:
Matt> Under Linux, try using gdb and running the 'debug' version
Matt> of the JVM (e.g., 'java_g' rather than 'java').
Matt> My .gdbinit has the following:
Matt> set env THREADS_TYPE=green_threads
Matt> set env JAVA_HOME /home/cs/mdw/src/java/dow
No, 'dbx' is a debugger similar to 'gdb'. It's not a Java debugger like
jdb.
Under Linux, try using gdb and running the 'debug' version of the JVM
(e.g., 'java_g' rather than 'java').
My .gdbinit has the following:
set env THREADS_TYPE=green_threads
set env JAVA_HOME /home/cs/mdw/src/java
Hi folks!
This one is stumping me: Has anyone been able to debug JNI code on Linux?
I am having absolutely zero success :-/
I've been trying to follow the debugging examples in Rob Gordon's
Essential JNI, and can not get any of them to work (on either NT or
Linux). He refers to dbx for Solaris..
