Terminate program hitting CTRL+C within GDB

gdb mingw
Benjamin picture Benjamin · Oct 17, 2011 · Viewed 14.9k times · Source

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?

Answer

Employed Russian picture Employed Russian · Oct 17, 2011

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.

Related questions

How do I use the MinGW gdb debugger to debug a C++ program in Windows?

I have looked for documentation on this and found nothing. I have MinGW installed and it works great. I just don't know how to use the debugger. Given some simple code, say in a file called "mycode.cpp": int main() { …

Read More
Adding gdb to MinGW

I've gone to http://sourceforge.net/project/showfiles.php?group_id=2435, downloaded the Automated MinGW Installer for MinGW 5.1.4 and at the same time the GNU Source-Level Debugger Release Candidate: GDB 6.8-3. I've then installed MinGW base tools into C:\MinGW. …

Read More
Core dump file analysis

What are all the things I will need to check while analyzing a core dump file? Please tell me from scratch.

Read More