From: Bob Wilson <bwilson@tensilica.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] fix typos in GDB docs
Date: Fri, 23 Mar 2007 23:00:00 -0000 [thread overview]
Message-ID: <46045C19.1020502@tensilica.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
I've been reviewing Tensilica's version of the GDB documentation and found a
number of minor problems to fix. I dare say some of these are obvious, but as
promised, I'm going to err on the side of caution and ask permission before
committing anything. I'll start with the easiest ones first.
2007-03-23 Bob Wilson <bob.wilson@acm.org>
* gdb.texinfo (File Options): Add missing parenthesis.
(Breakpoints, Special Fortran commands, PowerPC): Fix typos.
[-- Attachment #2: gdb-doc-typos.patch --]
[-- Type: text/plain, Size: 1855 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.389
diff -u -r1.389 gdb.texinfo
--- gdb.texinfo 26 Feb 2007 20:10:17 -0000 1.389
+++ gdb.texinfo 23 Mar 2007 22:54:00 -0000
@@ -886,7 +886,7 @@
When @value{GDBN} starts, it reads any arguments other than options as
specifying an executable file and core file (or process ID). This is
the same as if the arguments were specified by the @samp{-se} and
-@samp{-c} (or @samp{-p} options respectively. (@value{GDBN} reads the
+@samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the
first argument that does not have an associated option flag as
equivalent to the @samp{-se} option followed by that argument; and the
second argument that does not have an associated option flag, if any, as
@@ -2824,7 +2824,7 @@
operate. A breakpoint range is either a single breakpoint number, like
@samp{5}, or two such numbers, in increasing order, separated by a
hyphen, like @samp{5-7}. When a breakpoint range is given to a command,
-all breakpoint in that range are operated on.
+all breakpoints in that range are operated on.
@menu
* Set Breaks:: Setting breakpoints
@@ -9675,7 +9675,7 @@
@item info common @r{[}@var{common-name}@r{]}
This command prints the values contained in the Fortran @code{COMMON}
block whose name is @var{common-name}. With no argument, the names of
-all @code{COMMON} blocks visible at current program location are
+all @code{COMMON} blocks visible at the current program location are
printed.
@end table
@@ -15117,7 +15117,7 @@
@end table
@cindex SDS protocol
-The following commands specify to the SDS protocol are supported
+The following commands specific to the SDS protocol are supported
by@value{GDBN}:
@table @code
next reply other threads:[~2007-03-23 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 23:00 Bob Wilson [this message]
2007-03-24 17:12 ` Eli Zaretskii
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=46045C19.1020502@tensilica.com \
--to=bwilson@tensilica.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