| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2172389 | 7 | Coleen Phillimore | P2 | Closed | Fixed | b42 |
| JDK-2172846 | 6u14 | Coleen Phillimore | P3 | Closed | Fixed | b01 |
Hotspot now uses a separate version number from the overall JRE. It is useful to include both version tags in the crash error message and hs_err log.
The full hs_err log does include the library version in one place, e.g.:
"vm_info: Java HotSpot(TM) Client VM (11.0-b11) for windows-x86 JRE (1.6.0_10-b199)..."
(It's at the bottom of the file.)
However the error message printed to the screen, as well as the header of the hs_err, don't include the libraries version, e.g.:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x08abac20, pid=1008, tid=2504
#
# Java VM: Java HotSpot(TM) Client VM (10.0-b19 mixed mode windows-x86)
# Problematic frame:
# v ~BufferBlob::vtable chunks
We should consider adding the JRE version in at least these 2 places.
The full hs_err log does include the library version in one place, e.g.:
"vm_info: Java HotSpot(TM) Client VM (11.0-b11) for windows-x86 JRE (1.6.0_10-b199)..."
(It's at the bottom of the file.)
However the error message printed to the screen, as well as the header of the hs_err, don't include the libraries version, e.g.:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x08abac20, pid=1008, tid=2504
#
# Java VM: Java HotSpot(TM) Client VM (10.0-b19 mixed mode windows-x86)
# Problematic frame:
# v ~BufferBlob::vtable chunks
We should consider adding the JRE version in at least these 2 places.
- backported by
-
JDK-2172389 Hotspot crash error message should include libraries version
-
- Closed
-
-
-
- Closed
-