How do I get more debugging info from a JVM crash?

I'm experiencing a JVM crash running my webapp on Tomcat 4.1.18 with J2SE 1.4.1_02 on Windows 2000 SP3.

When the crash happens I get the following error:

****************

Another exception has been detected while we were handling last error.

Dumping information about last error:

ERROR REPORT FILE = (N/A)

PC= 0x2BE5C46D

SIGNAL= -1073741819

FUNCTION NAME= (N/A)

OFFSET= 0xFFFFFFFF

LIBRARY NAME= (N/A)

Please check ERROR REPORT FILE for further information, if there is any.

Good bye.

This doesn't tell me that much. Does anyone know how to extract more information out of a JVM crash? A stack trace would be great!

[701 byte] By [bitshiftera] at [2007-9-28 14:16:00]
# 1
did you try -verbose option of JVM?
sshafarenkaa at 2007-7-12 10:40:33 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...
# 2
I just tried the -verbose option, but I just got the same exception report as before, which didn't really say much. I might try -verbose:jni.Any other ideas would be appreciated!
bitshiftera at 2007-7-12 10:40:33 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...
# 3
We found the error report files in C:/WINNT/system32! Shame this behaviour doesn't seem to be documented anywhere.
bitshiftera at 2007-7-12 10:40:33 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...