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
compiled with the -g option.
As I suggested before, you can insert a dummy native method in your code
which traps the debugger. Calling this method forces the native code to
be loaded, returns you to the gdb prompt, and voila! You can set breakpoints.
You can also use the gdb 'load' command to force the symbols for your
shared object to be loaded into gdb, allowing you to set breakpoints.
Matt Welsh
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
