Windows Crash Dump is memory dump of a process running on a Windows system. These dumps can be very useful for debugging Java process crashes. In this entry I discuss how to collect sane Crash Dumps for Java process crashes on Windows machines that can later be analyzed using Windbg or other 'Debugging Tools For Windows'.
I have a simple java class test
which uses native library test.dll
using JNI. test.dll
implements a 'native' method where it accesses a null pointer and causes a crash. Complete source of this crashing program is hereWindows NT, 2000 and XP
Let's first run this program on a Windows NT/2000/XP machine:
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x10011f68, pid=2020, tid=640
# Java VM: Java HotSpot(TM) Client VM (10.0-b19 mixed mode, sharing windows-x86)
# Problematic frame:
# C [test.dll+0x11f68]
# An error report file with more information is saved as:
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Running this program created an hs_err log file in the same folder. Error log file contains the following stack trace:
Now, let's run it with -XX:+ShowMessageBoxOnError
JVM option. I get the following message box:
Attaching Visual Studio
to this process or collecting a crash dump with Dr Watson
and opening that crash dump with Windbg shows the following call trace:
This shows JVM's error handling frames and does not show that the crash happened in function test.f()
This is because, by default, the First Chance Exceptions are not sent to the System Debugger. And Debuggers receive only the Second Chance Exceptions. The exception in test.f() was a first Chance Exception that was hanlded by JVM. Please see details on First and Second chance exceptions: http://support.microsoft.com/kb/286350
So how can we collect crash dumps that contain the correct stack trace of the crash. Let's try 'adplus' to collect the crash dumps.
Start adplus in crash mode:
D:\\windbg>adplus -crash -pn java.exe
and then start your java process with -XX:+ShowMessageBoxOnError
By default, adplus creates mini dumps on First Chance Exceptions and full memory dumps on Second Chance Exceptions. It can be changed; details here: http://support.microsoft.com/kb/286350
'adplus' would create dump files in a folder like Crash_Mode__Date_08-12-2008__Time_15-12-56PM. Using Windbg, open the dump created at First Chance Exception and it shows the crashing frame as:
Ah! that's what I was looking for.Windows 2008 and Windows Vista
Dr. Watson is not available on Windows 2008 and Windows Vista
Starting with Windows Server 2008 and Windows Vista Service Pack1 (SP1), Windows has new error reporting mechanism called 'Windows Error Reporting' or WER. WER can be configured so that full user-mode dumps are collected and stored locally after a user-mode application crashes. This feature is not enabled by default. Enabling this feature requires administrator privileges. To enable and configure the feature, we need to use the following registry values under the
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps key.
And yes, here also we can use 'adplus' to collect Crash Dumps for First Chance and Second Chance Exceptions.
Enjoy Debugging !