RFR: 8141445: Use of Solaris/SPARC M7 libadimalloc.so can generate unknown signal in hs_err file (original) (raw)

Gerald Thornbrugh gerald.thornbrugh at oracle.com
Tue Nov 10 14:47:18 UTC 2015

Hi Everyone,

I have made the changes that David Holmes and Dan Daugherty suggested, below is the webrev:

http://cr.openjdk.java.net/~gthornbr/8141445/webrev.01/ <http://cr.openjdk.java.net/~gthornbr/8141445/webrev.01/>

Please let me know if you have any questions or concerns.

Thanks,

Jerry

On Nov 4, 2015, at 2:15 PM, Gerald Thornbrugh <gerald.thornbrugh at oracle.com> wrote:

Hi Everyone, Please review my fix for JDK-8141445. JDK-8141445 describes an issue seen only on Solaris/SPARC M7 hardware running Solaris 11.3 or later when the libadimalloc.so library is preloaded before running the JVM and the JVM crashes due to a memory allocation fault triggered by libadimalloc.so. Currently when libadimalloc.so triggers a memory allocation fault the SIGSEGV sicode is displayed as “unknown" in the hserr file. This change adds additional sicode defines so the memory allocation faults that trigger the JVM to core are displayed correctly in the hserr file. The changes also include a test that preloads the libadimalloc.so library, generates a libadimalloc.so memory allocation fault that crashes the JVM and then verifies that the correct sicode information is displayed in the hserr file. Webrev: http://cr.openjdk.java.net/~gthornbr/8141445/webrev.00/ <http://cr.openjdk.java.net/~gthornbr/8141445/webrev.00/> Bug: https://bugs.openjdk.java.net/browse/JDK-8141445 <https://bugs.openjdk.java.net/browse/JDK-8141445> Please let me know if you have any questions or concerns. Thanks, Jerry

More information about the hotspot-runtime-dev mailing list