No way to know when VICE stops because of AdvanceInstruction
Versatile Commodore Emulator
Brought to you by:
blackystardust,
gpz
i wonder, is there actually a situation that makes the monitor stop, which is NOT either checkpoint or stepping (aka advance instruction)?
Poking around in the monitor code now... it looks like the monitor doesn't even "know" why it opened shrug
ok so, i think the best idea to solve this, will be adding an extra parameter to monitor_startup(), which can be used to determine what called it, and then send this as extra info in the 0x62 response. I'll have to play around a bit to see if that makes sense. It'll also have to wait until after the big remove-mmu-translate patch was merged :)