Re:Why is there a “V” in SIGSEGV Segmentation Fault?
by rkeene2 on Thursday June 18, 2020 @10:42PM
(#23570473)
I started a project similar to the fictional "skip instructions that cause segmentation violations" for SIGILL (illegal instruction) which tried to implement SSE3 replacements on hosts without SSE3. It had two modes: replace the illegal instruction in memory, or handle it in the signal handler:
https://github.com/rkeene/sse3-emu