JDK-7033100 : CreateMinidumpOnCrash does not work for failed asserts
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs20
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: windows
- CPU: generic
- Submitted: 2011-04-01
- Updated: 2011-07-29
- Resolved: 2011-05-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | Other |
|---|---|
7Fixed  |
hs21Fixed |
Description
Starting with -XX:+CreateMinidumpOnCrash and running into an assert will cause a zero-length .mdmp file to be created and no error message to be reported. The problem is that when we call MiniDumpWriteDump we expect there to be siginfo and context information available (there is for "real" crashes). Whwn the information is not avilable we call MiniDumpWriteDump with an incorrect MINIDUMP_EXCEPTION_INFORMATION which causes it to crash and we get a recursive crash in the crash handling code. The fix is to call MiniDumpWriteDump with a NULL MINIDUMP_EXCEPTION_INFORMATION when context is not available.
Comments
|