-
Bug
-
Resolution: Fixed
-
P4
-
11, 12, 13
-
b24
-
solaris
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8225924 | 14 | Thomas Stuefe | P4 | Resolved | Fixed | team |
| JDK-8226629 | 11.0.5 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
os::signal(), on Solaris, does not specify SA_SIGINFO. This leads to signal handlers installed with this function - among others, the secondary signal handler installed during error reporting - to be called without siginfo_t pointer.
All other platforms specify SA_SIGINFO in os::signal(), and so does the Solaris-specific code which installs the "big" primary signal handler.
At SAP we run with this fix (specifying SA_SIGINFO on Solaris too) since years without problems.
All other platforms specify SA_SIGINFO in os::signal(), and so does the Solaris-specific code which installs the "big" primary signal handler.
At SAP we run with this fix (specifying SA_SIGINFO on Solaris too) since years without problems.
- backported by
-
JDK-8225924 [Solaris] os::signal() should call sigaction() with SA_SIGINFO
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-