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

Use of Solaris/SPARC M7 libadimalloc.so can generate unknown signal in hs_err file

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • P4
    • Resolution: Fixed
    • 9
    • 9
    • hotspot
    • Solaris/SPARC M7 platform running 11.3 or later.

    • b96
    • sparc_64
    • solaris_11

    Backports

      Description

        If the libadimalloc.so Solaris/SPARC M7 library is preloaded and a malloc'ed buffer is used after it is freed the libadmalloc.so library will generate a SIGSEGV with an unknown si_code. The libadimalloc.so library can generate three new si_codes that are currently not recognized:

        3 - "SEGV_ACCADI" "ADI not enabled for mapped object."
        4 - "SEGV_ACCDERR" "ADI disrupting exception."
        5 - "SEGV_ACCPERR" "ADI precise exception."

        These error codes need to be recognized by the JVM signal handling code and appropriate descriptions need to be printed in the hs_err file when these new si_codes are encountered.

        Attachments

          Issue Links

            Activity

              People

                gthornbr Gerald Thornbrugh (Inactive)
                gthornbr Gerald Thornbrugh (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: