just some debug stuff
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 :)
Poking around in the monitor code now... it looks like the monitor doesn't even "know" why it opened shrug
No way to know when VICE stops because of AdvanceInstruction
i wonder, is there actually a situation that makes the monitor stop, which is NOT either checkpoint or stepping (aka advance instruction)?
aaand another, this also has scpu fixed (hopefully). So it should be ready now... if someone would look over it and check if there are no stupid mistakes that would be nice :)
updated - fixed c128, scpu memory peek is still missing
1571 VIA1 PA reads missing bits