diff options
| author | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-07 21:33:37 +0000 |
|---|---|---|
| committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-07 21:33:37 +0000 |
| commit | fd32a1ddc0ab08ab71b6c24e4940d5d2cecccf33 (patch) | |
| tree | 705046ea40b37f50e62f414797680561b7e55a9b /gdb | |
| parent | c2d751d5e51893b95c86ada0899d8ed74f4ba9a7 (diff) | |
| download | fsf-binutils-gdb-fd32a1ddc0ab08ab71b6c24e4940d5d2cecccf33.zip fsf-binutils-gdb-fd32a1ddc0ab08ab71b6c24e4940d5d2cecccf33.tar.gz fsf-binutils-gdb-fd32a1ddc0ab08ab71b6c24e4940d5d2cecccf33.tar.bz2 | |
* 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.
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/doc/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 15 |
2 files changed, 18 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index d9ef9de..470a1d9 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +Thu Oct 7 16:15:37 1993 Jim Kingdon (kingdon@lioth.cygnus.com) + + * 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. + Wed Oct 6 13:23:01 1993 Tom Lord (lord@rtl.cygnus.com) * libgdb.texinfo: added `@' to braces that were unescaped. 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 |