You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would certainly find it useful if there was a call stack so I can see where a sub-routine has been invoked from in the code. Some are called in multiple places in the code. The stack is a mess most of the time so not that useful just to inspect it (variables written for caching etc) - but if it's possible to capture the calling location on JMP/JSR/Interrupts and remove on RTS/RTI etc and not too much work it'd set this significantly apart from other emulators for debugging.
Maybe with the state of the 6502 registers at the point of call too (slippery slope I know)? Guess it's a simple C array fixed to 256 entries no bigger than the stack that only holds JMP/JSR values and pops them when there's a return etc plus interrupts. Similar for registers.
Thank you!
The text was updated successfully, but these errors were encountered:
I would certainly find it useful if there was a call stack so I can see where a sub-routine has been invoked from in the code. Some are called in multiple places in the code. The stack is a mess most of the time so not that useful just to inspect it (variables written for caching etc) - but if it's possible to capture the calling location on JMP/JSR/Interrupts and remove on RTS/RTI etc and not too much work it'd set this significantly apart from other emulators for debugging.
Maybe with the state of the 6502 registers at the point of call too (slippery slope I know)? Guess it's a simple C array fixed to 256 entries no bigger than the stack that only holds JMP/JSR values and pops them when there's a return etc plus interrupts. Similar for registers.
Thank you!
The text was updated successfully, but these errors were encountered: