The Sinclair QL Forum

By the way, here's one application I have with a memory dump of the process. I am adapting my own mem viewer tool to the QL. By taking snapshots at regular intervals, I can take a look at the evolution of in-memory bitmaps (here, the intermediary bitmap when a piece if moved)

Fair enough. I'd say don't add the feature just for me. In my case, I combine some debugging operations (break in some functions, go step by step) with a memory dump.

As far as debugger UI, you don't necessarily need something with bells and whistles. If you look at MAME you'll see that the ...

Got it, thanks. It works now.

My next question is: how to enter the debugger?

I assume you're talking about https://github.com/xXorAa/sQ68Lay ?

For this emulator I wasn't able to get anywhere as I wasn't even able to insert any microdrive file (the -l option doesn't seem to accept .mdv files). Is there a documentation somewhere?

By debugging Q-Emulator using Windows kernel debugger (windbg) I was able to dump a memory snapshot of the QL onto disk. Not the most straightforward process by any mean but at least it does the job. Which allowed me to understand how the animation of MatchPoint is made.

I am still interested if ...

Derek_Stewart wrote: Fri Jun 27, 2025 10:23 pm Hi,

Have tried zesarux:

https://github.com/chernandezba/zesarux

which also has emulation debugger.

I did try this one, and it does seem to have some of the debugging features I'm looking for. However I was not able to get it to recognize .mdv files.

Thank you for the suggestions, I took a look at them. Because I'm trying to understand how existing games work, I'm not sure if a debugger running inside the emulator would work well.

Q-Emulator does have a debugger, however limited. For example, there doesn't seem to be a way to add a watchpoint ...

TRAP #0 enters supervisor mode. You should not use it, unless you really know what you are doing. A job needs to stay in user mode for normal scheduling.


Yes, I understand this. I used this code to to sync with the vblank. This works fine in a single-program case, but of course not in a ...

By starting from a program which does nothing but which works and adding more code I was able to figure out what was wrong: the `trap #0` code (switch to superviser mode) doesn't mix well with the multitasking.

This works now and I have two programs running in parallel and I can change the priority ...

Hang on, I just though of something. I'll try later tonight. But thanks for confirming it should work with QOS 1.1