1.2.13.1 Intercepting Signals (handle)

Change the way the debugger handles signal signal. signal
can be the number of a signal or its name (with or without the
SIG at the beginning); The keywords say what change to
make.

The keywords allowed by the handle command can be abbreviated.
Their full names are:

stop

The debugger should stop your program when this signal happens. This implies
the print keyword as well.

nostop

The debugger should not stop your program when this signal happens. It may
still print a message telling you that the signal has come in.

print

The debugger should print a message when this signal happens.

noprint

The debugger should not mention the occurrence of the signal at all.

pass

The debugger should allow your program to see this signal; your program
can handle the signal, or else it may terminate if the signal is fatal
and not handled. pass and noignore are synonyms.

nopass

The debugger should not allow your program to see this signal.
nopass and ignore are synonyms.

stack

The debugger should print a stack trace when it receives the
signal. When used with ``nostop'', this can be useful if you've got a
program that seems ``hung'' and you want to find out where it is, but
continue after showing this information.

nostack

The debugger should not print a stack trace when it receives the signal.