-
Bug
-
Resolution: Fixed
-
P3
-
11, 12
-
b15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8212690 | 11.0.2 | Martin Doerr | P3 | Resolved | Fixed | b02 |
I had contributed some improvements for the error reporting step "printing register info" with JDK-8207342.
But there are still parts which crash too easily. Oop and klass checks should get improved.
I have seen
"[error occurred during error reporting (printing register info), id 0xe0000000, Internal Error (/openjdk/jdk/src/hotspot/share/oops/klass.inline.hpp:63)]"
when using -XX:+CrashGCForDumpingJavaThread with recent jdk12.
"[error occurred during error reporting (printing register info)" can also be found in many hs_err files in the internet. This change is supposed to help people to investigate the root cause of crashes by providing the register info much more reliably.
But there are still parts which crash too easily. Oop and klass checks should get improved.
I have seen
"[error occurred during error reporting (printing register info), id 0xe0000000, Internal Error (/openjdk/jdk/src/hotspot/share/oops/klass.inline.hpp:63)]"
when using -XX:+CrashGCForDumpingJavaThread with recent jdk12.
"[error occurred during error reporting (printing register info)" can also be found in many hs_err files in the internet. This change is supposed to help people to investigate the root cause of crashes by providing the register info much more reliably.
- backported by
-
JDK-8212690 print_location is not reliable enough (printing register info)
- Resolved
- relates to
-
JDK-8219459 oopDesc::is_valid() is broken
- Resolved
-
JDK-8147512 Cleanups and improvements for print_location
- Closed