Stepping in the simulator no longer works for me (Intel Mac, Ventura 13.4.1 (c))

Since updating to 6.2.1 (although I'm starting to think thats not relevant), I can still set breakpoints that trigger. If I then hit "go", things work as expected, and it runs until the next breakpoint. Similarly "step out" will run until the current function exits (or the next breakpoint is hit).

But step and step into no longer work. The tool palette changes to show the pause button (as if the simulator is running), but it doesn't reach the next line. And if I look at the simulator, I can tell that it's not running (ie it didn't just treat the "step" as "go"). If I then hit the pause button, it will stop on the next line. But now the simulator is "broken". Whether I hit go, step or step out, it behaves just like step did (ie the palette changes to show the pause button, but the simulator makes no progress until I hit the pause button, at which point it stops on the next line).

I assumed it was a problem with 6.2.1, but downgrading through all versions down to 4.1.5 doesn't change the behavior (and I know for certain that 4.1.5, and at least some of the 4.2.x versions worked).

I've tried multiple projects, including some of the samples, and the behavior is the same. Once I step, the only thing I can do is step; and even then I have to hit pause to complete each step.

[edit:

I've tried using mdd from the command line, and I find that after stopping at a breakpoint, it (correctly) reports something like "Hit breakpoint 1, onUpdate () at HRMultifieldView.mc:79". But "step" or "next" report: "Cannot step when location is unknown."

If I then do "bt" (to show the backtrace) or "info frame" (to show the current location, locals and arguments), "step" and "next" start working.

I'm thinking this is probably related to the problem

]

[edit2:

It's the result of a change in VSCode. Stepping works in 1.78.2, but fails in 1.79.2 and later.

Presumably something changed in the debugger protocol. Its not clear whether its a bug in VSCode, or whether Garmin's debug server needs to be updated

]