Debugging a segmentation fault when I do ctrl c

debugging gdb copy-paste
Eduardo picture Eduardo · Feb 16, 2009 · Viewed 10.5k times · Source

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.

Answer

Charlie Martin picture Charlie Martin · Feb 16, 2009

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.

Related questions

How do I analyze a program's core dump file with GDB when it has command-line parameters?

My program operates like this: exe -p param1 -i param2 -o param3 It crashed and generated a core dump file, core.pid. I want to analyze the core dump file by gdb ./exe -p param1 -i param2 -o param3 core.…

Read More
How do I print the full value of a long string in gdb?

I want to print the full length of a C-string in GDB. By default it's being abbreviated, how do I force GDB to print the whole string?

Read More
How do I pass a command line argument while starting up GDB in Linux?

I have to debug a program that has errors in it as part of my assignment. However, I must first pass command line arguments in order to solve this problem. I do: gdb -tui InsertionSortWithErrors which works, but after that …

Read More