Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - Call Stack #32

Open
ajgbarnes opened this issue Jul 26, 2021 · 0 comments
Open

Feature Request - Call Stack #32

ajgbarnes opened this issue Jul 26, 2021 · 0 comments

Comments

@ajgbarnes
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant