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
We currently never return from SIGSEGV and other hardware exception handlers on Unix. We process the exception and resume execution somewhere. This is problematic on some Unixes like Illumos where not returning from the handler skips some of the bookkeeping stuff that the return from the handler does. For example, the alternate stack is not used after a first invocation of the SIGSEGV handler on Illumos (and if we ever moved to signals for handling hardware exceptions on macOS, it has similar problem).
Consider changing the hardware exception handling to return from the signal handler redirected to a helper function instead.
The text was updated successfully, but these errors were encountered:
We currently never return from SIGSEGV and other hardware exception handlers on Unix. We process the exception and resume execution somewhere. This is problematic on some Unixes like Illumos where not returning from the handler skips some of the bookkeeping stuff that the return from the handler does. For example, the alternate stack is not used after a first invocation of the SIGSEGV handler on Illumos (and if we ever moved to signals for handling hardware exceptions on macOS, it has similar problem).
Consider changing the hardware exception handling to return from the signal handler redirected to a helper function instead.
The text was updated successfully, but these errors were encountered: