JDK-8074552 : SafeFetch32 and SafeFetchN do not work in error handling
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-03-06
  • Updated: 2015-06-03
  • Resolved: 2015-03-13
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 9
9 b57Fixed
Related Reports
Relates :  
JDK-8076185 - Provide SafeFetch implementation for zero
Relates :  
JDK-8075533 - Zero JVM segfaults for -version after JDK-8074552
Description
SafeFetch32 and SafeFetchN could be very useful in error reporting, e.g. to print out hex dumps of potentially invalid memory locations. 

However, using them will just cause a secondary crash and a "Error during error handling" message in the error log. 

They need to be handled in the secondary signal handlers like they are handled in the primary ones.
Comments
Note that SafeFetch does still not work in error handling for the zero platform. This is still open, but considered of low importance for now.
31-03-2015