JDK-8217994 : os::print_hex_dump should be more resilient against unreadable memory
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11,12,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-29
  • Updated: 2022-09-15
  • Resolved: 2019-01-30
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.
JDK 11 JDK 12 JDK 13
11.0.3Fixed 12.0.2Fixed 13 b06Fixed
Related Reports
Relates :  
JDK-8293851 - hs_err should print more stack in hex dump
Relates :  
JDK-8217879 - hs_err should print more instructions in hex dump
Relates :  
JDK-8257828 - SafeFetch may crash if invoked in non-JavaThreads
Relates :  
JDK-8219650 - [TESTBUG] Fix crashes in new test hotspot gtest "test_print_hex_dump"
Description
Today, accidentally calling os::print_hex_dump on unreadable memory would SEGV. It would probably be the second SEGV in the error reporting code that wants to dump some raw memory. We can use os::is_readable_pointer to query readable memory before reading it. For example:
 http://cr.openjdk.java.net/~shade/8217994/webrev.01/
Comments
Fix Request Backporting this fix would allow better post-mortem quality of hs_errs and debuggability. Fix applies cleanly to both 11u and 12u, passes tier1 testing, and new gtest.
14-02-2019
URL: http://hg.openjdk.java.net/jdk/jdk/rev/556122252316 User: shade Date: 2019-01-30 18:49:18 +0000
30-01-2019
RFR: http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-January/036488.html
29-01-2019