Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082507 | emb-9 | David Holmes | P4 | Resolved | Fixed | team |
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.
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.
- backported by
-
JDK-8082507 SafeFetch32 and SafeFetchN do not work in error handling
-
- Resolved
-
- relates to
-
JDK-8076185 Provide SafeFetch implementation for zero
-
- Resolved
-
-
JDK-8075533 Zero JVM segfaults for -version after JDK-8074552
-
- Resolved
-
-
JDK-8075860 aarch64 fails to build
-
- Resolved
-