Skip to main content
Thom Key
Visitor II
October 7, 2019
Question

Program randomly pauses and refuses to run after (handle_vCont_t, Thread already stopped)

  • October 7, 2019
  • 12 replies
  • 5424 views

Hey ST,

I've recently migrated to STM32CubeIDE as live variables tracking sounded very appealing to me.

Sadly this also has a (major) issue with debugging.

Let's say I had set a debug point at a certain line, 150 or so.

I think I removed it, afterwards if I run the debugger the program will run, but will consistently stop at 150.

I can verify this as I can pause it and see it being stuck there.

It will then say "handle_vCont_t, Thread already stopped".

The program will now not run, whether I use Resume, Step into or Step over.

The only way around this is to set a breakpoint before this and manually pass this line (instruction) with Step over.

This is incredibly annoying as I am trying to check timing with a logic analyzer.

I've tried some things, from using a different ST-LINK (V2 <> V3), to doing a clean all to creating and using a new debug configuration.

It seems as if there's a rogue breakpoint still there.

Any way around this?

I tried restarting STM32CubeIDE, but that didn't work.

Edit: The manual method doesn't work anymore :(

Edit2: OpenOCD works fine. But then I lose some tools...

This topic has been closed for replies.

12 replies

CBrin.3
Visitor II
September 27, 2021

Had the same problem, looks like the culprit was the Live Expressions... Go to Debug Configurations, under the Debugger tab, under Misc I just disabled the Live Expressions. Tadaah

Adrian Adamson
Senior
December 16, 2022

I tried switching back and forth and it didn't help. But OpenOCD did say that the target had 6 breakpoints and 4 watchpoints. (Edit: I figured out since then that that doesn't mean how many are activated, but just what it is capable of) I just want to know where the watchpoint information is stored so I can blow it away without having to de-install and re-install the IDE.