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

Print correct and more information about secondary errors.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 11
    • 11
    • hotspot
    • None
    • b20

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

              stuefe Thomas Stuefe
              stuefe Thomas Stuefe
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: