GDB: Ctrl+C doesn't interrupt process as it usually does but rather terminates the program

Question

Normally when you run a program through GDB you can press Ctrl+C to interrupt it, e.g. if it gets stuck in an infinite loop and you want to get a backtrace.

I\'m deb

Answer 1

In the gdb prompt you can do "handle SIGINT stop" so that gdb catches CTRL-C