Program received signal SIGTRAP, Trace/breakpoint trap in atollic true studio

Question

I'm new to the atollic truestudio. I have running a C code for STM32 MCU, but unfortunately the code stops its execution at the same point everytime when I debug the code even though there is no breakpoint applied. I have attached an image below for reference. Could anyone tell me how to resolve this breakpoint trap issue.

Thank you

Answer 1

This question is a bit old now, but if someone finds it like I did trying to solve this problem:-

The trigger seems to be trying to add too many breakpoints.

The fix was:

• Disconnect the ST-LINK debugger,
• Remove power from the board
• Then restart everything.

I suspect there is a breakpoint register somewhere in the core that the debugger "forgets" about, and it needs a power cycle to clear that register.