archive.worldofdragon.org

On Linux, I'd just run xroar as: xroar -trace >trace.txt xroar writes its trace output to stdout using printf, so this is just redirecting stdout to a file rather than the screen. It looks like you're on Windows from the screenshots above, so I don't know if the same will work there (although > usua...

If you run xroar with the -trace option, it'll print every instruction it executes to stdout. You can redirect that to a file and then search through it afterwards. (You can turn tracing on and off at runtime too, but disk space is plentiful these days...) If it's not obvious from the trace, you mig...

In MAME's debugger, how about using a watchpoint that catches all memory accesses, but with a condition that limits it to the range you want by reading the pointer? e.g.