Native Code

If your application makes calls to its own native code, the debug JVM will automatically add a _g to the name of all native libraries that are loaded with System.loadLibrary. You will need to ensure that a copy of your native libraries with the required _g suffix (eg. myNativeLib_g.dll or libmyNativeLib_g.so) exists in the library search path or else you will receive UnsatisfiedLinkErrors when your application is run.

Note that it is not possible to step through the native code within BugSeeker as BugSeeker can only help you to debug the java code portion of your program. To debug native code, you will have to resort to using your platforms native debugger. It may be possible to simultaneously debug native and java portions of your program if you can configure your native debugger to run your program using the debug JVM and then remotely connect BugSeeker to this remote VM after supply the proper JPDA connection parameters. Please consult the Remote Debugging section of this guide for more information on how to setup a remote debugging session.