Rationale
Create a standard extensible crash screen, since this should really be handled at the OS level.
Existing work
HackerSM64 PR #888 is basically what we're going for here. Shows the registers, asserts, stack trace, disasm, etc.
Extensions from that baseline would include:
- User configurable page where you pass in a callback to show a custom view (e.g. Kirby 64 uses this to show the current
GObjs and their fields, as well as the current process and the last decompressed block).
- RSP debugging?
This would require devs to integrate a tool into their build system to be able to see symbol names.
Rationale
Create a standard extensible crash screen, since this should really be handled at the OS level.
Existing work
HackerSM64 PR #888 is basically what we're going for here. Shows the registers, asserts, stack trace, disasm, etc.
Extensions from that baseline would include:
GObjs and their fields, as well as the current process and the last decompressed block).This would require devs to integrate a tool into their build system to be able to see symbol names.