From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [commit/doc] Fix typo in description of "set remotebreak" command
Date: Thu, 17 Nov 2005 19:27:00 -0000 [thread overview]
Message-ID: <20051117121257.26550db3@ironwood.lan> (raw)
Committed as obvious...
* gdb.texinfo (Remote Configuration): Fix typo in description of
"set remotebreak" command.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.292
diff -u -p -r1.292 gdb.texinfo
--- gdb.texinfo 16 Nov 2005 10:34:33 -0000 1.292
+++ gdb.texinfo 17 Nov 2005 19:04:48 -0000
@@ -12149,7 +12149,7 @@ Show the current speed of the remote con
@cindex BREAK signal instead of Ctrl-C
If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote
when you press the @key{Ctrl-C} key to interrupt the program running
-on the remote. If set to off, @value{GDBN} sends the @samp{Strl-C}
+on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C}
character instead. The default is off, since most remote systems
expect to see @samp{Ctrl-C} as the interrupt signal.
next reply other threads:[~2005-11-17 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 19:27 Kevin Buettner [this message]
2005-11-17 19:32 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051117121257.26550db3@ironwood.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox