On Fri, Apr 13, 2012 at 10:39:24AM -0500, Christopher Pow wrote: > Not done yet: > 1. Memory dialog doesn't yet allow setting memory. > 2. SID register dialog is incomplete, does not yet show actual memory > values, or setting memory values. > 3. No VIC-II or CIA register dialogs yet. > 4. CPU register dialog doesn't show I/O 0/1 yet, and NMI/IRQ/RESET > vectors are not filled in. > 5. Breakpoints sometimes get hit while the emulator is being told to > "run" which leaves the UI buttons in an inconsistent state. My TCP > comms needs a bit of work yet. > 6. I haven't yet moved to the binary memory retrieval command provided > by Spiro to speed up memory updating on CPU stepping. For now CPU Hmm, I had to missed something, it seems. How does it work exactly? Does anybody has a complete up-to-date documentation on monitor, especially new features, etc? > stepping does not update memory--otherwise stepping would be > ridiculously slow. Memory is updated whenever a breakpoint is hit, Hmm. I am not sure it would work at all, but VICE may be able to give information about the changed memory byte by an opcode in stepping mode at least. So only a single byte should be sent. Surely, there are "ugly" things like altering the memory configuration etc by an opcode, then it's not so simple anymore (maybe it could be signaled, and a full memdump is needed, hmm I am not sure how frequent the case when memory configuration is changed rapidly when this cause a slowdown because of dumping full memory). Btw, is stepping really slow with memory update? I mean, stepping is for tracing a program for humans, I can't see too much point to do more quickier than eg max of 0.1sec/step. Or is it even slower? And as far as I see the problem you may need to update only the memory part which is shown for the user actually, if memory window is "scrolled" etc, then other parts can be transferred on-demand. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Apr 13 19:27:26 2012
This archive was generated by hypermail 2.1.8 : 2012-04-13 19:27:29 CEST