Peter S. Hollander

Also voicing support for offline access to free GitLens+ features! It is unexpected to have access to features while developing a repository locally, only for those features to be taken...

Thanks for your response @eamodio - That is my current approach, however this validation is the only piece of my VSCode installation which requires internet access, and I would look...

> It suggests I'm using 0.12.0. I am also using 0.12.0 of stock OpenOCD (on Windows) > From what little I understand of the issue, I believe this is all...

I have identified a third workaround - passing `monitor reset` to gdb (the "DEBUG CONSOLE" tab in VSCode) when the timers are erroniously paused allows me to debug as inteded...

So I gave `monitor reset init` a try, but unfortunately that does not resolve the frozen timers in my environment either. So far for gdb commands, only the `monitor reset`...

Update: I spun up a fresh install of Debian Bookworm this weekend, and I can confirm that this timer freezing occurs in Debian as well, even when following the exact...

I understand the cause of the issue! Stock OpenOCD 0.12.0, as available through `apt` or the pre-built Windows binary, is the problem. Specifically commits [e877d52](https://github.com/raspberrypi/openocd/commit/e877d521d97b1756a3916772cc8e9f38fd1b277e) and [9a9dbf8](https://github.com/raspberrypi/openocd/commit/9a9dbf876aead6c165cecb3deb5878b08f58f651) in Raspberry Pi's...

Do you develop on a Raspberry Pi? I have a hunch that maybe Raspberry Pi OS packages the custom fork of OpenOCD. You can loosely check if your OpenOCD has...

(I acknowledge that this change may be controversial as it changes the default optimization of debug builds, so please consider this pull request with caution)

By "pre-build Windows binary" I'm talking about the official OpenOCD release binaries as built by the OpenOCD Organization (specifically 0.12.0, which is the most recent version at the time of...