b2
b2 copied to clipboard
tom-seddon
Show call stack
I realise this is not always going to work (since some code plays with the stack in non-obvious ways), but when stepping through code in the debugger it's useful to see the addresses of where the current routine was called from (and if in future symbols are available, then use those).
I realised you could guess which addresses are return addresses by seeing if there was a $20 (jsr) in the right place. Additional heuristics are also possible.
I've so far avoided having the CPU leave some kind of byte provenance indicators for the debugger, but that could also be an option.
If you're still using b2, and don't mind building it yourself, this can be found on the /wip/tom branch. It'll make its way into a release in due course (the quality bar for the /wip/tom is not very high, but it is the build I use myself).