There are none that I know of, although I'd be most interested to learn if I am wrong!!! The main problem, as you are aware, is that once the code switches from Java to native, information regarding the Java stack trace is lost. So you might know that a JNI method has caused a memory leak, but it's harder to track down. And, since you don't have the code to the JVM implementation, you don't have a point of reference for debugging all of the native code...

That said, I have had limited sucess with using standard native debuggers/core file analysis tools in Unix. Perhaps an NT equivalent would help you. Maybe you should refer to the Rational website - something in their catalog might be of use to you...

Dermot