问题
I get a segmentation fault when I cancel my program. I am using gdb for debugging, the problem is that when I press Ctrl-C while I am debugging gdb does not cancel the program and do what it is supposed to do that is stop it.
What I want is do the Ctrl-C and do not allow gdb to stop it. Is there any way to do this? Any other recommendations for debugging? I cannot use printf because sincerely I have not a clear idea where the problem comes from.
回答1:
gdb is intercepting the signal. When you press CTRL-C, you're actually causing the terminal driver to generate a SIGINT.
What you need to do is have GDB generate the SIGINT using the signal command. the syntax is
signal num
and man signal will tell you the signal number (in this case, SIGINT is signal 2, so signal 2 will do it.)
Update
Sure enough, you can use the symbolic name. info signal will tell you all the names etc.
Oh, by the way, odds are that you have a signal handler installed for SIGINT and the arguments aren't right somehow.
回答2:
An alternative is to stop gdb from catching the SIGINT by typing handle SIGINT noprint pass at the gdb prompt before running the program.
回答3:
One option is to load the core file produced when not running in the debugger into gdb. From within gdb, type core-file [filename].
回答4:
You can also send the CTRL-C (aka SIGINT) from another terminal: kill -INT
来源：https://stackoverflow.com/questions/553956/debugging-a-segmentation-fault-when-i-do-ctrl-c