STM32CubeIDE: Breakpoints inactive after optimized build then non-optimized build.

Garnett.Robert · ‎2021-03-20

Hi,

After getting a realtime project working with optimization set to -o (No optimizations) I set optimizations on for both the C and C++ compilers. I ran the system successfully did some profiling then restored optimizations back to -o for further development work and debugging.

After this the debugging points were disabled.

I checked the build log and it showed optimization as -o. I re-indexed and did a full build, but still the breakpoints were disabled. I can step through the code from start-up and all of the statements are executed in order so the code hasn't been optimized out such that the breakpoints should be disabled.

Can someone help with this?

Best regards

Rob

Garnett.Robert · ‎2021-03-20

Silly Me

I must have hit the disable breakpoints button. That is why all breakpoints were slashed out.

It's hard to get good "help" isn't it.