JDK-8248321 : [JVMCI] improve libgraal logging and fatal error handling
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11,15,16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-06-25
- Updated: 2021-01-04
- Resolved: 2020-07-02
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 11 | JDK 16 |
|---|---|
| 11.0.9-oracleFixed | 16 b05Fixed  |
Related Reports
|
Relates :
|
Description
Logging output from libgraal for options such as -Dlibgraal.PrintGC=true currently goes to stderr. Instead, this should go to HotSpot's tty stream. Likewise, a fatal error in libgraal currently routes directly to call the libc abort function. Instead, it should call HotSpot's report_fatal function so that a proper hs_err_pid crash log is produced. This crash log should also contain relevant JVMCI events that may help diagnose a libgraal crash.
Comments
|