cube ide strange breakpoint behaviour

[john_love_stm]

Using cube IDE to debug my application i've witnessed breakpoints behaving unpredictably: sometimes they appear on their own in breakpoint list view while not present in the file editing view; other times the breakpoints i've just placed and just used dissapear.
What can be a cause of such behaviour and how can i prevent it from happening?

[Ghofrane GSOURI]

Hello @john_love_stm 

First let me thank you for posting.

Could you please provide more details about the STM32CubeIDE version that you are using as well as your OS.

THX

Ghofrane

[john_love_stm]

Hello, @Ghofrane GSOURI
First let me thank you for replying.
My OS is Windows 11 and my STM32CubeIDE version is 1.14.1.

[Ozone]

Not a Cube IDE user, but ...

Are you sure the debug artifact and source code match ?
Have you tried a clean, and full rebuild ?

[Ghofrane GSOURI]

Hello @john_love_stm 

I recommend you to use the latest STM32CubeIDE version 1.18.1 rather than 1.14.1

THX

Ghofrane

[john_love_stm]

I don't think i understand your question. What do you mean by "debug artifact"?
Hard to tell if full rebuild would help since the issue happens randomly with and wihtout rebuilding

[Ozone]

> I don't think i understand your question. What do you mean by "debug artifact"?

The ELF / HEX / BIN file created by the toolchain, which is executed on the target.
"Build artifact" is a common term for any files created during the build process.

> Hard to tell if full rebuild would help since the issue happens randomly with and wihtout rebuilding

This is somewhat difficult to judge from the outside.
Have you tried a different target board, or a different host PC ?

I would first try with copy of the project, either in another folder or on another PC. And perhaps a simple example project for your MCU.

Another option would be  Segger's Ozone (unrelated to my moniker here): https://www.segger.com/downloads/jlink/#Ozone
This is generic Cortex M debugger usable independant of any specific toolchain. Last time I checked, it was free for non-commercial projects. I'm not sure if it supports ST-Link directly, but you can reversibly flash a Segger firmware to onboard ST-Links to make it a J-Link.