Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8205925

Print correct and more information about secondary errors.

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 11
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b20

      Backports

        Description

        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)]

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  stuefe Thomas Stuefe
                  Reporter:
                  stuefe Thomas Stuefe
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: