darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

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

Browse source 
and add a section explaining the difference between the GDB
	signal command and the shell kill utility.
This commit is contained in:
Jim Kingdon 1993-10-07 21:33:37 +00:00
parent c2d751d5e5
commit fd32a1ddc0
2 changed files with 18 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gdb/doc/ChangeLog
View file

@ -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.

15
gdb/doc/gdb.texinfo
View file

@ -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