-
Bug
-
Resolution: Fixed
-
P4
-
9
-
Solaris/SPARC M7 platform running 11.3 or later.
-
b96
-
sparc_64
-
solaris_11
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8156284 | 8u111 | Gerald Thornbrugh | P4 | Closed | Fixed | b01 |
| JDK-8149721 | 8u102 | James Cheng | P4 | Closed | Fixed | b04 |
| JDK-8162081 | emb-8u111 | Gerald Thornbrugh | P4 | Resolved | Fixed | b01 |
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.
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.
- backported by
-
JDK-8162081 Use of Solaris/SPARC M7 libadimalloc.so can generate unknown signal in hs_err file
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-