Resume execution where your program is stopped, but immediately give it the
signal signal. The signal can be the name or the number of a
signal. For example, on many systems
signal 2 and
SIGINT are both ways of sending an interrupt signal.
Alternatively, if signal is zero, continue execution without
giving a signal. This is useful when your program stopped on account of
a signal and would ordinarily see the signal when resumed with the
continue command; ‘signal 0’ causes it to resume without a
Note: When resuming a multi-threaded program, signal is delivered to the currently selected thread, not the thread that last reported a stop. This includes the situation where a thread was stopped due to a signal. So if you want to continue execution suppressing the signal that stopped a thread, you should select that same thread before issuing the ‘signal 0’ command. If you issue the ‘signal 0’ command with another thread as the selected one, GDB detects that and asks for confirmation.
signal does not repeat when you press RET a second time
after executing the command.
signal command is not the same as invoking the
kill utility from the shell. Sending a signal with
causes GDB to decide what to do with the signal depending on
the signal handling tables (see Signals). The
passes the signal directly to your program.