OpenGOAL Debugger - Stack Frames

[water111]

The debugger should understand stack frames so you can do up to see the calling function.

[water111]

https://github.com/water111/jak-project/pull/658 adds basic support for backtraces to :di. Still need up and down to work.

[Zedb0T]

for the stack frames: that's been partially implemented. the compiler saves information about stack frames so the debugger can display a stack trace and try to unwind. But the interface to see this is pretty bad - just a giant list of functions and a little snippet of code from each. try running the debugger, and insert a random (crash!) in the code to get a stacktrace. The remaining work is to make a nice way to see at a glance, all the calling functions, and to go up/down and get some context for each. https://discord.com/channels/756287461377703987/756287461830688810/1074158861109448735