Contents|Index|Previous|Next
Giving
your program a signal
The
following documentation discusses GDB’s
signal
command.
signalsignal
Resume execution where your
program stopped, but immediately give it the signal signal.
signal
can be the name or the number of a signal. For example, on many systems
signal
2 and signalSIGINT
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 ordinary see the
signal when resumed with the continue
command; ‘signal 0’
causes it to resume without a signal.
signal
does not repeat when you use Return
a second time after executing the command.
Invoking the signal
command is not the same as invoking the kill
utility from the shell. Sending a signal with kill
causes GDB to decide what to do with the signal depending on the signal
handling tables (see Signals).
The signal
command passes the signal directly to your program.
Top|Contents|Index|Previous|Next