Completely unrelated questions, but: (1) if I disable interrupts temporarily so that I can use the stack pointer for pixel plotting, is there any reliable way to spot afterwards if I've missed an end-of-display interrupt? I'm vaguely aware that there's a "current scanline" hardware counter somewhere — does that count actual PAL lines or only lines with pixels on them? And how long does the end-of-display interrupt signal last? My memory is saying 24 cycles, but I'm not sure why. I guess since we're on a system with no explicit interrupt acknowledgments, it's going to be something tiny?
(2) over in Acornland we're currently discussing a remote debugging protocol, the primary purpose of which is to allow an emulator to emulate while a separate debugger connects to the emulator and tracks/adjusts state, etc. Currently the thinking is to go all modern and JSON + HTTPy about it (so you could even write a debugger in Javascript if you wanted, we're not dependant on any system-specific inter-process communications and the sort of languages you'd want to write a debugger in already know how to do most of the communication tasks), but I wondered if anybody here is aware of any existing emulators or standards that implement anything like that?
