You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On s390x, SIGILL, SIGFPE, and SIGTRAP are delivered with the PSW address pointing after the faulting instruction, while SIGSEGV and SIGBUS are delivered with the PSW address pointing to the faulting instruction.
This behavior effectively forms part of the kernel ABI. Given that the ABI already has a section 1.5 Exception Interface that documents the relationship between architecture exceptions and kernel signals, we should add the information about where the reported PSW points to depending on the signal type to that chapter as well.
The text was updated successfully, but these errors were encountered:
On s390x, SIGILL, SIGFPE, and SIGTRAP are delivered with the PSW address pointing after the faulting instruction, while SIGSEGV and SIGBUS are delivered with the PSW address pointing to the faulting instruction.
This behavior effectively forms part of the kernel ABI. Given that the ABI already has a section 1.5 Exception Interface that documents the relationship between architecture exceptions and kernel signals, we should add the information about where the reported PSW points to depending on the signal type to that chapter as well.
The text was updated successfully, but these errors were encountered: