* gdb.texinfo (Signaling): Update for symbolic symbol names

	and add a section explaining the difference between the GDB
	signal command and the shell kill utility.

1 files changed, 12 insertions, 3 deletions

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index e6168de..341187f 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6264,12 +6264,14 @@ already executed, in order to examine its execution in more detail.
 @section Giving your program a signal
 
 @table @code
-@item signal @var{signalnum}
+@item signal @var{signal}
 @kindex signal
 Resume execution where your program stopped, but immediately give it the
-signal number @var{signalnum}.
+signal @var{signal}.  @var{signal} can be the name or the number of a
+signal.  For example, on many systems @code{signal 2} and @code{signal
+SIGINT} are both ways of sending an interrupt signal.
 
-Alternatively, if @var{signalnum} is zero, continue execution without
+Alternatively, if @var{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
 @code{continue} command; @samp{signal 0} causes it to resume without a
@@ -6279,6 +6281,13 @@ signal.
 after executing the command.
 @end table
 @c @end group
+
+Invoking the @code{signal} command is not the same as invoking the
+@code{kill} utility from the shell.  Sending a signal with @code{kill}
+causes @value{GDBN} to decide what to do with the signal depending on
+the signal handling tables (@pxref{Signals}).  The @code{signal} command
+passes the signal directly to your program.
+
 @end ifclear
 
 @node Returning