Debugging JVM crash via JNI Invocation

Question

Our software is causing a JVM crash with an EXCEPTION_FLT_STACK_CHECK error using the latest
Sun 1.4.2 and 5.0 JVMs on Windows XP. No such error appears with 1.4 on Macintosh OS X.
We start the JVM via JNI Invocation - our software is a plug-in for a standard Windows GUI program that
requires a C++ interface. How can we get a crash dump or otherwise see what is going on when we
crash? We don't have a chance to catch a Java exception. It seems to be crashing within a very generic
call to the Xerces 2.6.2 XML parser.
When we use the "-XX:+ShowMessageBoxOnError" option invoking the JVM, we do see a message box
on the JVM error. Using the "-Xcheck:jni" option shows no problems. I tried viewing the JVM in jconsole,
which worked nicely, but adding the "-Dcom.sun.management.jmxremote" option makes the crash
go away.
I feel like I've likely missed something obvious in my web and reference searches, but on the other hand
JNI invocation information can be in short supply. This bug is 100% reproducible with a certain software
and data setup.
Thanks for any pointers and advice you can offer!
Michael

Answer 1

Thanks. Off list someone also pointed me to the Java troubleshooting guide at:
http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf
This is very helpful for giving instructions for creating a crash dump. Sun might be able to use it but I can't
seem to get any response to my JVM bug report, so I'm looking for something that might help me figure
out what the heck is going on. Is there a way to get a normal Java fatal error log via either
-XX:+ShowMessageBoxOnError or -XX:OnError?
Thanks again,
Michael