Add a keyboard shortcut to "Continue" the debugger

[trs-eric]

Clicking the continue button on the debugger is a little tedious, can you add a keyboard shortcut? Bonus points if the keyboard's repeat function works to keep repeatedly spamming the continue button.

Thank you for a great program!

[malbanGit]

The marked Icon is a button to "toggle" debug mode.
If the program is running and you press the button - you enter debugging mode.
If you are in debug mode - you "continue" to run the program. A repeat function for this makes no sense.

The "single Step" button right next to it is probably what you seek. Though there is no shortcut or repeat for that either.

A "repeat" function of the keyboard - I would rather refrain from using that - since it is OS buffered and the amount of repeats stored might be not what you are looking for, since you can easily pass the desired location.

It always helps to know what you are trying to achieve.

The single step feature is exactly that - a single step.
There also is an overstep (main purpose is for subroutines), and a step out functionality that migth help you.

There is also a "multi-step" function which more or less is the repeat you might be looking for.
The speed of the multi steps can be configure... well, in the configuration menu.

There are also heaps of breakpoints which might help you, even breakpoints that compare values in registers.

In the command line interface, you can also tell the debugger to run a certain amount of cycles, which might help with what you are trying to achieve.

---

I guess what you are asking for is a keyboard shortcut for the "single step" button.
-> I'll look into it. It is probably only a line or two.

[trs-eric]

Sorry that button doesn't have a label, it looks and works like a continue button.

I set a breakpoint and then continue to run the program and it stops on my breakpoint. I can then inspect the memory or registers or anything I like.

It's just annoying clicking a lot when I want to inspect say 100 or 300 iterations. I understand I can use the other multi step routines but I also like inspecting in this way.

Here's a video

debug.mp4

One key, like pressing F11 would be helpful to avoid all the clicking.

[malbanGit]

I see.
Ok - I implemented following keys:

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_SPACE,0, false), "set Breakpoint");
    jTableSource.getActionMap().put("set Breakpoint", new AbstractAction() { public void actionPerformed(ActionEvent e) {  if (currentDissi.vecxPanel==null) return; currentDissi.vecxPanel.debugBreakpointAction(); }});

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_R,0, false), "RUN");
    jTableSource.getActionMap().put("RUN", new AbstractAction() { public void actionPerformed(ActionEvent e) {  if (currentDissi.vecxPanel==null) return; currentDissi.vecxPanel.debugAction(); }});

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_S,0, false), "STEP");
    jTableSource.getActionMap().put("STEP", new AbstractAction() { public void actionPerformed(ActionEvent e) {  jButtonDebugStepActionPerformed(null); }});

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_O,0, false), "OVERSTEP");
    jTableSource.getActionMap().put("OVERSTEP", new AbstractAction() { public void actionPerformed(ActionEvent e) {  jButtonOverstepActionPerformed(null); }});

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_U,0, false), "STEPOUT");
    jTableSource.getActionMap().put("STEPOUT", new AbstractAction() { public void actionPerformed(ActionEvent e) {  jButtonStepOutActionPerformed(null); }});

    jTableSource.getInputMap(WHEN_FOCUSED).put(KeyStroke.getKeyStroke(KeyEvent.VK_D,0, false), "DEBUGTOGGLE");
    jTableSource.getActionMap().put("DEBUGTOGGLE", new AbstractAction() { public void actionPerformed(ActionEvent e) {  jButtonDebugActionPerformed(null); }});

You can download the jar with these changes under:

http://vectrex.malban.de/tmp/Vide2026_02_04.jar
(You have to change your vide.jar - make a backup...)

I might also point to the feature of "watches" you can add.
You can do so in the debugger.

But you can also use something similar to old school "printf" statements :-).
The "hey" dissi comments (look in the doc).

In short:
Within your assembler code write as a comment behind the line you are interested in something like:

; hey dissi "print value of $c9b5"

Than the value of that location will be output to the dissi screen whenever that location is executed.
You can also use labels, registers.

You can also add "permanent" watches with comments in your source, like:
; hey dissi "watch RecalCounter"

Again this is documented... if interested...