From ae606bee5b0808aaf3fe1cb80cc9ae6e877d6d46 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Thu, 15 Nov 2012 21:25:43 +0000 Subject: [PATCH] * gdb.texinfo (Signaling): Fix typo. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index dc0ca89..a774681 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2012-11-15 Tom Tromey + + * gdb.texinfo (Signaling): Fix typo. + 2012-11-13 Giuseppe Montalto * gdb.texinfo (GDB/MI Data Manipulation): Document new optional diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f45b65e..945a66b 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -15642,7 +15642,7 @@ SIGINT} are both ways of sending an interrupt signal. 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 +a signal and would ordinarily see the signal when resumed with the @code{continue} command; @samp{signal 0} causes it to resume without a signal. -- 2.7.4