Terminate program hitting CTRL+C within GDB

Question

My program is determined to stop its execution by hitting CTRL+C in command window. By now, I have a critical error right in this stopping phase, so i want to debug with gdb.

Problem is, gdb redefines CTRL+C as its own interrupt and pauses the execution when hitted. How can I handle it that CTRL+C powers my programm off and gdb can catch the stack trace?

Related: http://stackoverflow.com/q/6008140/694576 – alk Aug 06 '16 at 15:47 — alk, Aug 06 '16 at 15:47

score 69 · Accepted Answer · answered Oct 17 '11 at 16:21

69

From the (gdb) prompt, type signal SIGINT. This will send (surprize) SIGINT to the program being debugged.

Alternatively, handle SIGINT nostop print pass will make GDB pass the signal straight to the inferior (being debugged) process.

answered Oct 17 '11 at 16:21

Employed Russian

199,314
34
295
362

6

Ctrl-Z works in GDB: it suspends the process and gets you to that `(gdb)` prompt. – Felix Oct 05 '20 at 16:45

Terminate program hitting CTRL+C within GDB

1 Answers1