Proper exception handling

[fruityloops1]

Is there an existing issue for this?

• I have searched the existing issues

What feature are you suggesting?

Citra's code base by default attempts to completely ignore all invalid writes, invalid reads, invalid PC addresses, and other exceptions that happen in user space. This makes some games more ""stable"" by having certain crashes ignored and the game still runs fine. In all other cases, the state of the code that has generated the exception is obviously not going to work anymore if you try to continue running it, and will just loop generating the same exception to be ignored over and over again, clogging the log and leaving the emulator in a confusing, frozen state as it attempts to keep running this code that has already crashed.
The feature request would be the following:

• Implement proper crash handling (add a dolphin-esque popup detailing the crash that allows you to exit the emulation or ignore the exception, and also have a look at the full crash information with all of the registers)
• Implement arm11 exception handlers (function pointer in the TLS that is usually called by the kernel with a pre-configured stack when an exception occurs)
• Implement signals for the GDB stub that match the exception types (similar to luma's gdb)

Why would this feature be useful?

Without this feature, crashes are confusing for the end user, and literally undebuggable for homebrew/mod developers. It would also allow for custom crash handlers to run, instead of being ignored. This is more accurate and transparent.
(has this ever been addressed before? yuzu had the same problem…)