Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8206056 | 12 | Thomas Stuefe | P4 | Resolved | Fixed | team |
JDK-8206651 | 11.0.1 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
Daniel Daugherty, when solving JDK-8205648, remarked on the lack of error information for secondary errors, i.e. errors which occurr during error handling.
Currently we see:
[error occurred during error reporting (test secondary crash 1), id 0xb]
Which does not tell much, especially since the printed id is wrong, it is the id of the primary error, not the secondary one.
It would be helpful to see actually what error occurred during error reporting.
This patch adds the ability to see the correct secondary error, for secondary signals:
[error occurred during error reporting (test secondary crash 1), id 0x8, SIGSEGV (0xb) at pc=0x00007fb877815ca6]
and for secondary asserts:
[error occurred during error reporting (test secondary crash 1), id 0xe0000000, Internal Error (/shared/projects/openjdk/jdk-jdk/source/src/hotspot/share/utilities/vmError.cpp:1726)]
Currently we see:
[error occurred during error reporting (test secondary crash 1), id 0xb]
Which does not tell much, especially since the printed id is wrong, it is the id of the primary error, not the secondary one.
It would be helpful to see actually what error occurred during error reporting.
This patch adds the ability to see the correct secondary error, for secondary signals:
[error occurred during error reporting (test secondary crash 1), id 0x8, SIGSEGV (0xb) at pc=0x00007fb877815ca6]
and for secondary asserts:
[error occurred during error reporting (test secondary crash 1), id 0xe0000000, Internal Error (/shared/projects/openjdk/jdk-jdk/source/src/hotspot/share/utilities/vmError.cpp:1726)]
- backported by
-
JDK-8206056 Print correct and more information about secondary errors.
-
- Resolved
-
-
JDK-8206651 Print correct and more information about secondary errors.
-
- Resolved
-
- relates to
-
JDK-8205648 fix for 8205195 breaks secondary error handling
-
- Resolved
-