Program received signal SIGINT, Interrupt

[ashishgarag87]

Posted on September 23, 2016 at 11:06

Hi,

I am using STM32469I-Evaluation board (384KB SRAM and 2MB flash), Cube MX version 4.16, SW4STM and AC6 tool chain version 1.8v (32bit OS) and ST-Link V2.1 debugger (firmware version

V2.J27.M15

). I have created Led blinky project using CubeMx software for SW4STM and all works fine using ST-LINK V2.1 debugger, i can run and debug the code. The problem is that many times i am not able to debug the code by using breakpoints even without doing any modification in led blinky project

when there is problem i have seen ''Program received signal SIGINT, Interrupt'' message shown in debug window and the debugger does not stop at the desired breakpoint and doesn't halt at main but it is stuck in some loop.

Sometimes when message

''Program received signal SIGINT, Interrupt''

is not shown then debugger works properly. i am not able to understand the logic behind these message while debugging. Please guide me were i am going wrong while debugging. #debugging

[AvaTar]

Posted on September 23, 2016 at 12:35

> Sometimes when message

''Program received signal SIGINT, Interrupt''

is not shown then debugger works properly. ''Signal SIGINT'' relates to the POSIX signal interface, most probably to the gdb client of your toolchain. And not to the STM32 target. I don't use SW4STM, and can't tell more - perhaps the ST people can ...

[luciantodor]

Posted on September 23, 2016 at 12:38

I'm using STM32F0xxx and I have the same behavior with the STLink. It's not clear for me either what happens with STLink and OpenOCD.

My solution was to switch to JLink.