Geoff Winkless wrote:
Integration with SimCoupé to include clock-accurate debug stepping
We do have some of that already, with the raster accurate display updates when stepping, and tstate timings shown for instructions and stepped-over blocks. Should be easy to debug fancy display effects.
True source-level debugging is difficult without proper integration of the editor and assembler tools, and I'd definitely not want to edit source code inside SimCoupe. Even just having my text editor alongside while I'm single-stepping is a huge improvement on how it used to be.
A balance might be to have the assembler output label and source line information that the SimCoupe debugger can use to show portions of the original file. Or even just having known labels in the disassembly window would make quite a difference.
and real-time code reassembly? :)
To inject new code into a running SimCoupe, or something more? It would be nice to have a socket interface to the core, for debugger-like functions and other live tweaking. Maybe someone can write their own then ;-)
The pyz80 setup works well for me because it starts with a clean system each time, adding in the new code and data files I want in memory. That way I can be sure I've not corrupted anything and am not relying on some thing from the old state. For live injection there's still the Import feature, but that's only really convenient for occasionally importing single files.
Si
