typos in GDB manual
Ralf Wildenhues
Ralf.Wildenhues@gmx.de
Tue Jan 16 21:21:00 GMT 2007
Hello there,
Apparently my typo patch posted to bug-binutils a while ago,
<http://lists.gnu.org/archive/html/bug-binutils/2006-07/msg00055.html>
never made it into CVS. Here's an updated patch.
I'm not actually sure whether the `$cwdr' in gdb.texinfo:5183 is a
misspelling or not, but grepping the source suggests so.
Also, I guess it'd need to be
| The access size attributes tell @value{GDBN}
rather than `tells' in gdb.texinfo:6898?
A bit unsure about `partial' in gdb.texinfo:22633.
Cheers, please Cc: me on replies,
Ralf
2007-01-16 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* agentexpr.texi: Fix some typos.
* annotate.texinfo: Likewise.
* gdb.texinfo: Likewise.
* gdbint.texinfo: Likewise.
* observer.texi: Likewise.
* stabs.texinfo: Likewise.
Index: gdb/doc/agentexpr.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/agentexpr.texi,v
retrieving revision 1.6
diff -u -r1.6 agentexpr.texi
--- gdb/doc/agentexpr.texi 10 May 2006 18:49:08 -0000 1.6
+++ gdb/doc/agentexpr.texi 16 Jan 2007 21:19:36 -0000
@@ -17,7 +17,7 @@
@node Agent Expressions
@appendix The GDB Agent Expression Mechanism
-In some applications, it is not feasable for the debugger to interrupt
+In some applications, it is not feasible for the debugger to interrupt
the program's execution long enough for the developer to learn anything
helpful about its behavior. If the program's correctness depends on its
real-time behavior, delays introduced by a debugger might cause the
@@ -221,7 +221,7 @@
In this example, @code{add} is the name of the bytecode, and
@code{(0x02)} is the one-byte value used to encode the bytecode, in
-hexidecimal. The phrase ``@var{a} @var{b} @result{} @var{a+b}'' shows
+hexadecimal. The phrase ``@var{a} @var{b} @result{} @var{a+b}'' shows
the stack before and after the bytecode executes. Beforehand, the stack
must contain at least two values, @var{a} and @var{b}; since the top of
the stack is to the right, @var{b} is on the top of the stack, and
Index: gdb/doc/annotate.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/annotate.texinfo,v
retrieving revision 1.6
diff -u -r1.6 annotate.texinfo
--- gdb/doc/annotate.texinfo 23 Dec 2005 19:26:16 -0000 1.6
+++ gdb/doc/annotate.texinfo 16 Jan 2007 21:19:36 -0000
@@ -20,7 +20,7 @@
@set DATE July 2003
@c NOTE: cagney/2003-07-28:
-@c Don't make this migration doccument an appendix of GDB's user guide.
+@c Don't make this migration document an appendix of GDB's user guide.
@c By keeping this separate, the size of the user guide is contained. If
@c the user guide to get much bigger it would need to switch to a larger,
@c more expensive, form factor and would drive up the manuals publication
@@ -161,7 +161,7 @@
Any change to @value{GDBN}'s @sc{cli} output modifies or removes that
information and, consequently, likely breaks the client.
-Since the @sc{gdb/mi} output is independant of the @sc{cli}, it does not
+Since the @sc{gdb/mi} output is independent of the @sc{cli}, it does not
have this problem.
@section Scalability
@@ -200,8 +200,8 @@
statements with various annotations. As a consequence, any @sc{cli}
output change can alter the annotation output.
-Since the @sc{gdb/mi} output is independant of the @sc{cli}, and the
-@sc{gdb/mi} is increasingly implemented independant of the @sc{cli}
+Since the @sc{gdb/mi} output is independent of the @sc{cli}, and the
+@sc{gdb/mi} is increasingly implemented independent of the @sc{cli}
code, its long term maintenance is much easier.
@node Migrating to GDB/MI
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.378
diff -u -r1.378 gdb.texinfo
--- gdb/doc/gdb.texinfo 11 Jan 2007 20:42:40 -0000 1.378
+++ gdb/doc/gdb.texinfo 16 Jan 2007 21:19:47 -0000
@@ -3217,7 +3217,7 @@
the underlying system supports them. (Note that hardware-assisted
watchpoints that were set @emph{before} setting
@code{can-use-hw-watchpoints} to zero will still use the hardware
-mechanism of watching expressiion values.)
+mechanism of watching expression values.)
@table @code
@item set can-use-hw-watchpoints
@@ -4664,7 +4664,7 @@
and is likely before the user entry point @code{main} (or equivalent) is called.
@item set backtrace past-entry off
-Backtraces will stop when they encouter the internal entry point of an
+Backtraces will stop when they encounter the internal entry point of an
application. This is the default.
@item show backtrace past-entry
@@ -5148,7 +5148,7 @@
For instance, a rule substituting @file{/usr/source} into
@file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but
not to @file{/usr/sourceware/foo-2.0}. And because the substitution
-is applied only at the begining of the directory name, this rule will
+is applied only at the beginning of the directory name, this rule will
not be applied to @file{/root/usr/source/baz.c} either.
In many cases, you can achieve the same result using the @code{directory}
@@ -5181,7 +5181,7 @@
@kindex cdir
@kindex cwd
@vindex $cdir@r{, convenience variable}
-@vindex $cwdr@r{, convenience variable}
+@vindex $cwd@r{, convenience variable}
@cindex compilation directory
@cindex current directory
@cindex working directory
@@ -6171,7 +6171,7 @@
@item set print repeats
@cindex repeated array elements
Set the threshold for suppressing display of repeated array
-elelments. When the number of consecutive identical elements of an
+elements. When the number of consecutive identical elements of an
array exceeds the threshold, @value{GDBN} prints the string
@code{"<repeats @var{n} times>"}, where @var{n} is the number of
identical repetitions, instead of displaying the identical elements
@@ -6382,8 +6382,8 @@
@item set print pascal_static-members
@itemx set print pascal_static-members on
-@cindex static members of Pacal objects
-@cindex Pacal objects, static members display
+@cindex static members of Pascal objects
+@cindex Pascal objects, static members display
Print static members when displaying a Pascal object. The default is on.
@item set print pascal_static-members off
@@ -6830,7 +6830,7 @@
Define a memory region bounded by @var{lower} and @var{upper} with
attributes @var{attributes}@dots{}, and add it to the list of regions
monitored by @value{GDBN}. Note that @var{upper} == 0 is a special
-case: it is treated as the the target's maximum memory address.
+case: it is treated as the target's maximum memory address.
(0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.)
@item mem auto
@@ -6895,7 +6895,7 @@
@end table
@subsubsection Memory Access Size
-The acccess size attributes tells @value{GDBN} to use specific sized
+The access size attributes tells @value{GDBN} to use specific sized
accesses in the memory region. Often memory mapped device registers
require specific sized accesses. If no access size attribute is
specified, @value{GDBN} may use accesses of any size.
@@ -11326,7 +11326,7 @@
@cindex calling functions
@cindex inferior functions, calling
@item print @var{expr}
-Evaluate the expression @var{expr} and display the resuling value.
+Evaluate the expression @var{expr} and display the resulting value.
@var{expr} may include calls to functions in the program being
debugged.
@@ -11773,7 +11773,7 @@
symbols from shared libraries. To that end, type @kbd{set
auto-solib-add off} before running the inferior, then load each
library whose debug symbols you do need with @kbd{sharedlibrary
-@var{regexp}}, where @var{regexp} is a regular expresion that matches
+@var{regexp}}, where @var{regexp} is a regular expression that matches
the libraries whose symbols you want to be loaded.
@kindex show auto-solib-add
@@ -11879,9 +11879,9 @@
is used after @samp{sysroot} fails to locate the library, or if the
path to the library is relative instead of absolute. If you want to
use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set
-@samp{sysroot} to a nonexistant directory to prevent @value{GDBN} from
+@samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from
finding your host's libraries. @samp{sysroot} is preferred; setting
-it to a nonexistant directory may interfere with automatic loading
+it to a nonexistent directory may interfere with automatic loading
of shared library symbols.
@kindex show solib-search-path
@@ -12497,7 +12497,7 @@
@section Connecting to a remote target
On the @value{GDBN} host machine, you will need an unstripped copy of
-your program, since @value{GDBN} needs symobl and debugging information.
+your program, since @value{GDBN} needs symbol and debugging information.
Start up @value{GDBN} as usual, using the name of the local copy of your
program as the first argument.
@@ -12766,7 +12766,7 @@
@table @code
@item set remoteaddresssize @var{bits}
-@cindex adress size for remote targets
+@cindex address size for remote targets
@cindex bits in remote address
Set the maximum size of address in a memory packet to the specified
number of bits. @value{GDBN} will mask off the address bits above
@@ -13653,7 +13653,7 @@
It takes an optional argument that is evaluated to
a long value to give the information about this given selector.
Without argument, this command displays information
-about the the six segment registers.
+about the six segment registers.
@kindex info dll
@item info dll
@@ -13996,7 +13996,7 @@
This command shows the state of current thread suspension.
@item set thread run
-This comamnd sets whether the current thread is allowed to run.
+This command sets whether the current thread is allowed to run.
@item show thread run
Show whether the current thread is allowed to run.
@@ -14664,7 +14664,7 @@
@item set download-path @var{path}
@kindex set download-path
@cindex find downloadable @sc{srec} files (M32R)
-Set the default path for finding donwloadable @sc{srec} files.
+Set the default path for finding downloadable @sc{srec} files.
@item show download-path
@kindex show download-path
@@ -15008,7 +15008,7 @@
@table @code
@kindex hwatch
@item hwatch @var{conditional}
-Set hardware watchpoint on combination of Load/Store Effecive Address(es)
+Set hardware watchpoint on combination of Load/Store Effective Address(es)
or Data. For example:
@code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)}
@@ -15073,7 +15073,7 @@
@end table
@cindex SDS protocol
-The following commands specifi to the SDS protocol are supported
+The following commands specify to the SDS protocol are supported
by@value{GDBN}:
@table @code
@@ -15695,13 +15695,13 @@
@subsection HPPA
@cindex HPPA support
-When @value{GDBN} is debugging te HP PA architecture, it provides the
+When @value{GDBN} is debugging the HP PA architecture, it provides the
following special commands:
@table @code
@item set debug hppa
@kindex set debug hppa
-THis command determines whether HPPA architecture specific debugging
+This command determines whether HPPA architecture specific debugging
messages are to be displayed.
@item show debug hppa
@@ -16500,11 +16500,11 @@
end
define hook-continue
-handle SIGLARM pass
+handle SIGALRM pass
end
@end smallexample
-As a further example, to hook at the begining and end of the @code{echo}
+As a further example, to hook at the beginning and end of the @code{echo}
command, and to add extra text to the beginning and end of the message,
you could define:
@@ -17733,7 +17733,7 @@
follow development on @email{gdb@@sourceware.org} and
@email{gdb-patches@@sourceware.org}. There is also the mailing list
@email{dmi-discuss@@lists.freestandards.org}, hosted by the Free Standards
-Group, which has the aim of creating a a more general MI protocol
+Group, which has the aim of creating a more general MI protocol
called Debugger Machine Interface (DMI) that will become a standard
for all debuggers, not just @value{GDBN}.
@cindex mailing lists
@@ -17871,7 +17871,7 @@
following line is passed to @sc{gdb/mi} as input, while @samp{<-} means
the output received from @sc{gdb/mi}.
-Note the the line breaks shown in the examples are here only for
+Note the line breaks shown in the examples are here only for
readability, they don't appear in the real output.
@subheading Setting a breakpoint
@@ -18232,7 +18232,7 @@
@item -r
Insert a regular breakpoint in all the functions whose names match the
given regular expression. Other flags are not applicable to regular
-expresson.
+expressions.
@end table
@subsubheading Result
@@ -18380,12 +18380,12 @@
@end smallexample
Create a watchpoint. With the @samp{-a} option it will create an
-@dfn{access} watchpoint, i.e. a watchpoint that triggers either on a
+@dfn{access} watchpoint, i.e., a watchpoint that triggers either on a
read from or on a write to the memory location. With the @samp{-r}
-option, the watchpoint created is a @dfn{read} watchpoint, i.e. it will
+option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will
trigger only when the memory location is accessed for reading. Without
either of the options, the watchpoint created is a regular watchpoint,
-i.e. it will trigger when the memory location is accessed for writing.
+i.e., it will trigger when the memory location is accessed for writing.
@xref{Set Watchpoints, , Setting watchpoints}.
Note that @samp{-break-list} will report a single list of watchpoints and
@@ -18604,7 +18604,7 @@
If blanks are needed as
part of a directory name, double-quotes should be used around
the name. In the command output, the path will show up separated
-by the system directory-separator character. The directory-seperator
+by the system directory-separator character. The directory-separator
character must not be used
in any directory name.
If no directories are specified, the current search path is displayed.
@@ -18654,7 +18654,7 @@
If blanks are needed as
part of a directory name, double-quotes should be used around
the name. In the command output, the path will show up separated
-by the system directory-separator character. The directory-seperator
+by the system directory-separator character. The directory-separator
character must not be used
in any directory name.
If no directories are specified, the current path is displayed.
@@ -19420,7 +19420,7 @@
@table @samp
@item @var{level}
-The frame number, 0 being the topmost frame, i.e. the innermost function.
+The frame number, 0 being the topmost frame, i.e., the innermost function.
@item @var{addr}
The @code{$pc} value for that frame.
@item @var{func}
@@ -19521,7 +19521,7 @@
type and value for simple data types and the name and type for arrays,
structures and unions. In this last case, a frontend can immediately
display the value of simple data types and create variable objects for
-other data types when the the user wishes to explore their values in
+other data types when the user wishes to explore their values in
more detail.
@subsubheading @value{GDBN} Command
@@ -20019,7 +20019,7 @@
@item @var{linenum}
is the line number to disassemble around
@item @var{lines}
-is the the number of disassembly lines to be produced. If it is -1,
+is the number of disassembly lines to be produced. If it is -1,
the whole function will be disassembled, in case no @var{end-addr} is
specified. If @var{end-addr} is specified as a non-zero value, and
@var{lines} is lower than the number of disassembly lines between
@@ -20044,7 +20044,7 @@
@end itemize
Note that whatever included in the instruction field, is not manipulated
-directely by @sc{gdb/mi}, i.e. it is not possible to adjust its format.
+directly by @sc{gdb/mi}, i.e., it is not possible to adjust its format.
@subsubheading @value{GDBN} Command
@@ -21496,7 +21496,7 @@
similar programs which want to interact with @value{GDBN} at a
relatively high level.
-The annotation mechanism has largely been superseeded by @sc{gdb/mi}
+The annotation mechanism has largely been superseded by @sc{gdb/mi}
(@pxref{GDB/MI}).
@ignore
@@ -21536,7 +21536,7 @@
@option{--annotate} command line option (@pxref{Mode Options}), controls
how much information @value{GDBN} prints together with its prompt,
values of expressions, source lines, and other types of output. Level 0
-is for no anntations, level 1 is for use when @value{GDBN} is run as a
+is for no annotations, level 1 is for use when @value{GDBN} is run as a
subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable
for programs that control @value{GDBN}, and level 2 annotations have
been made obsolete (@pxref{Limitations, , Limitations of the Annotation
@@ -21865,7 +21865,7 @@
@c should add a web page ref...
In any event, we also recommend that you submit bug reports for
-@value{GDBN}. The prefered method is to submit them directly using
+@value{GDBN}. The preferred method is to submit them directly using
@uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
be used.
@@ -22118,7 +22118,7 @@
directory.
If you have @TeX{} and a @sc{dvi} printer program installed, you can
-typeset and print this manual. First switch to the the @file{gdb}
+typeset and print this manual. First switch to the @file{gdb}
subdirectory of the main source directory (for example, to
@file{gdb-@value{GDBVN}/gdb}) and type:
@@ -22521,7 +22521,7 @@
@kindex maint demangle
@item maint demangle @var{name}
-Demangle a C@t{++} or Objective-C manled @var{name}.
+Demangle a C@t{++} or Objective-C mangled @var{name}.
@kindex maint deprecate
@kindex maint undeprecate
@@ -22555,7 +22555,7 @@
These commands take an optional parameter @var{message-text} that is
used as the text of the error or warning message.
-Here's an example of using @code{indernal-error}:
+Here's an example of using @code{internal-error}:
@smallexample
(@value{GDBP}) @kbd{maint internal-error testing, 1, 2}
@@ -22658,7 +22658,7 @@
This command prints, for each object file in the program, various data
about that object file followed by the byte cache (@dfn{bcache})
statistics for the object file. The objfile data includes the number
-of minimal, partical, full, and stabs symbols, the number of types
+of minimal, partial, full, and stabs symbols, the number of types
defined by the objfile, the number of as yet unexpanded psym tables,
the number of line tables and string tables, and the amount of memory
used by the various tables. The bcache statistics include the counts,
@@ -23265,7 +23265,7 @@
@item vCont?
@cindex @samp{vCont?} packet
-Request a list of actions supporetd by the @samp{vCont} packet.
+Request a list of actions supported by the @samp{vCont} packet.
Reply:
@table @samp
@@ -24624,7 +24624,7 @@
@subsection Console I/O
@cindex console i/o as part of file-i/o
-By default and if not explicitely closed by the target system, the file
+By default and if not explicitly closed by the target system, the file
descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output
on the @value{GDBN} console is handled as any other file output operation
(@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled
Index: gdb/doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.249
diff -u -r1.249 gdbint.texinfo
--- gdb/doc/gdbint.texinfo 4 Jan 2007 19:42:10 -0000 1.249
+++ gdb/doc/gdbint.texinfo 16 Jan 2007 21:19:51 -0000
@@ -284,7 +284,7 @@
need to support @sc{dwarf}'s Call Frame Information in mind. In fact,
the term ``unwind'' is taken directly from that specification.
Developers wishing to learn more about unwinders, are encouraged to
-read the the @sc{dwarf} specification.
+read the @sc{dwarf} specification.
@findex frame_register_unwind
@findex get_frame_register
@@ -1054,7 +1054,7 @@
The first time a command is used the user will be warned and offered a
replacement (if one exists). Note that the replacement string passed to
-@code{deprecate_cmd} should be the full name of the command, i.e. the
+@code{deprecate_cmd} should be the full name of the command, i.e., the
entire string the user should type at the command line.
@section UI-Independent Output---the @code{ui_out} Functions
@@ -2929,7 +2929,7 @@
its name.
@end deftypefn
@deftypefn {Target Macro} int ADDRESS_CLASS_NAME_to_TYPE_FLAGS (int @var{name}, int *var{type_flags_ptr})
-Given an address qualifier name, set the @code{int} refererenced by @var{type_flags_ptr} to the type flags
+Given an address qualifier name, set the @code{int} referenced by @var{type_flags_ptr} to the type flags
for that address class qualifier.
@end deftypefn
@@ -3104,7 +3104,7 @@
@cindex @code{struct value}, converting register contents to
@emph{Maintainer's note: The way GDB manipulates registers is undergoing
-significant change. Many of the macros and functions refered to in this
+significant change. Many of the macros and functions referred to in this
section are likely to be subject to further revision. See
@uref{http://sources.redhat.com/gdb/current/ari/, A.R. Index} and
@uref{http://www.gnu.org/software/gdb/bugs, Bug Tracking Database} for
@@ -3555,7 +3555,7 @@
@findex unwind_pc
@anchor{unwind_pc} Return the instruction address, in @var{this_frame}'s
caller, at which execution will resume after @var{this_frame} returns.
-This is commonly refered to as the return address.
+This is commonly referred to as the return address.
The implementation, which must be frame agnostic (work with any frame),
is typically no more than:
@@ -3572,7 +3572,7 @@
@item CORE_ADDR unwind_sp (struct frame_info *@var{this_frame})
@findex unwind_sp
@anchor{unwind_sp} Return the frame's inner most stack address. This is
-commonly refered to as the frame's @dfn{stack pointer}.
+commonly referred to as the frame's @dfn{stack pointer}.
The implementation, which must be frame agnostic (work with any frame),
is typically no more than:
@@ -3816,7 +3816,7 @@
@item struct type *register_type (@var{gdbarch}, @var{reg})
@findex register_type
If defined, return the type of register @var{reg}. This function
-superseeds @code{DEPRECATED_REGISTER_VIRTUAL_TYPE}. @xref{Target Architecture
+supersedes @code{DEPRECATED_REGISTER_VIRTUAL_TYPE}. @xref{Target Architecture
Definition, , Raw and Virtual Register Representations}.
@item REGISTER_CONVERT_TO_VIRTUAL(@var{reg}, @var{type}, @var{from}, @var{to})
@@ -3841,10 +3841,10 @@
Define this as 1 if the target does not have a hardware single-step
mechanism. The macro @code{SOFTWARE_SINGLE_STEP} must also be defined.
-@item SOFTWARE_SINGLE_STEP(@var{signal}, @var{insert_breapoints_p})
+@item SOFTWARE_SINGLE_STEP(@var{signal}, @var{insert_breakpoints_p})
@findex SOFTWARE_SINGLE_STEP
A function that inserts or removes (depending on
-@var{insert_breapoints_p}) breakpoints at each possible destinations of
+@var{insert_breakpoints_p}) breakpoints at each possible destinations of
the next instruction. See @file{sparc-tdep.c} and @file{rs6000-tdep.c}
for examples.
@@ -3925,7 +3925,7 @@
@findex DEPRECATED_POP_FRAME
@findex frame_pop
If defined, used by @code{frame_pop} to remove a stack frame. This
-method has been superseeded by generic code.
+method has been superseded by generic code.
@item push_dummy_call (@var{gdbarch}, @var{function}, @var{regcache}, @var{pc_addr}, @var{nargs}, @var{args}, @var{sp}, @var{struct_return}, @var{struct_addr})
@findex push_dummy_call
@@ -3976,7 +3976,7 @@
@findex SAVE_DUMMY_FRAME_TOS
@anchor{SAVE_DUMMY_FRAME_TOS} Used in @samp{call_function_by_hand} to
notify the target dependent code of the top-of-stack value that will be
-passed to the the inferior code. This is the value of the @code{SP}
+passed to the inferior code. This is the value of the @code{SP}
after both the dummy frame and space for parameters/results have been
allocated on the stack. @xref{unwind_dummy_id}.
@@ -4020,7 +4020,7 @@
parameter, and such a parameter should not be added. If an architecture
that requires per-compiler or per-function information be identified,
then the replacement of @var{rettype} with @code{struct value}
-@var{function} should be persued.}
+@var{function} should be pursued.}
@emph{Maintainer note: The @var{regcache} parameter limits this methods
to the inner most frame. While replacing @var{regcache} with a
@@ -4501,7 +4501,7 @@
stack), active but not running (pushed, but not connected to a fully
manifested inferior), or completely active (pushed, with an accessible
inferior). Most targets are only completely inactive or completely
-active, but some support persistant connections to a target even
+active, but some support persistent connections to a target even
when the target has exited or not yet started.
For example, connecting to the simulator using @code{target sim} does
@@ -4932,7 +4932,7 @@
chunks of memory. Each obstack is a pool of memory that is managed
like a stack. Objects (of any nature, size and alignment) are
allocated and freed in a @acronym{LIFO} fashion on an obstack (see
-@code{libiberty}'s documenatation for a more detailed explanation of
+@code{libiberty}'s documentation for a more detailed explanation of
@code{obstacks}).
The most noticeable use of the @code{obstacks} in @value{GDBN} is in
@@ -4941,7 +4941,7 @@
these @code{obstacks}: dictionary entries, blocks, blockvectors,
symbols, minimal symbols, types, vectors of fundamental types, class
fields of types, object files section lists, object files section
-offets lists, line tables, symbol tables, partial symbol tables,
+offset lists, line tables, symbol tables, partial symbol tables,
string tables, symbol table private data, macros tables, debug
information sections and entries, import and export lists (som),
unwind information (hppa), dwarf2 location expressions data. Plus
@@ -4950,7 +4950,7 @@
An essential and convenient property of all data on @code{obstacks} is
that memory for it gets allocated (with @code{obstack_alloc}) at
-various times during a debugging sesssion, but it is released all at
+various times during a debugging session, but it is released all at
once using the @code{obstack_free} function. The @code{obstack_free}
function takes a pointer to where in the stack it must start the
deletion from (much like the cleanup chains have a pointer to where to
@@ -4999,7 +4999,7 @@
Often it is necessary to manipulate a dynamic array of a set of
objects. C forces some bookkeeping on this, which can get cumbersome
-and repetative. The @file{vec.h} file contains macros for defining
+and repetitive. The @file{vec.h} file contains macros for defining
and using a typesafe vector type. The functions defined will be
inlined when compiling, and so the abstraction cost should be zero.
Domain checks are added to detect programming errors.
@@ -5495,7 +5495,7 @@
@item -Wformat-nonliteral
Non-literal format strings, with a few exceptions, are bugs - they
-might contain unintented user-supplied format specifiers.
+might contain unintended user-supplied format specifiers.
Since @value{GDBN} uses the @code{format printf} attribute on all
@code{printf} like functions this checks not just @code{printf} calls
but also calls to functions such as @code{fprintf_unfiltered}.
@@ -6031,7 +6031,7 @@
To avoid version conflicts, vendors are expected to modify the file
@file{gdb/version.in} to include a vendor unique alphabetic identifier
(an official @value{GDBN} release never uses alphabetic characters in
-its version identifer). E.g., @samp{6.2widgit2}, or @samp{6.2 (Widgit
+its version identifier). E.g., @samp{6.2widgit2}, or @samp{6.2 (Widgit
Inc Patch 2)}.
@section Experimental Branches
@@ -6406,8 +6406,8 @@
@item
@email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list}
@item
-@email{gdb@@sources.redhat.com, GDB Discsussion mailing list} and
-@email{gdb-testers@@sources.redhat.com, GDB Discsussion mailing list}
+@email{gdb@@sources.redhat.com, GDB Discussion mailing list} and
+@email{gdb-testers@@sources.redhat.com, GDB Discussion mailing list}
@end itemize
@emph{Pragmatics: The branch creation is sent to the announce list to
@@ -6614,7 +6614,7 @@
@emph{Don't worry about the @file{gdb.info-??} or
@file{gdb/p-exp.tab.c}. They were generated (and yes @file{gdb.info-1}
was also generated only something strange with CVS means that they
-didn't get supressed). Fixing it would be nice though.}
+didn't get suppressed). Fixing it would be nice though.}
@subsubheading Create compressed versions of the release
Index: gdb/doc/observer.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/observer.texi,v
retrieving revision 1.11
diff -u -r1.11 observer.texi
--- gdb/doc/observer.texi 10 May 2006 18:49:08 -0000 1.11
+++ gdb/doc/observer.texi 16 Jan 2007 21:19:51 -0000
@@ -74,7 +74,7 @@
@deftypefun extern struct observer *observer_attach_@var{event} (observer_@var{event}_ftype *@var{f})
Using the function @var{f}, create an observer that is notified when
-ever @var{event} occures, return the observer.
+ever @var{event} occurs, return the observer.
@end deftypefun
@deftypefun extern void observer_detach_@var{event} (struct observer *@var{observer});
Index: gdb/doc/stabs.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/stabs.texinfo,v
retrieving revision 1.19
diff -u -r1.19 stabs.texinfo
--- gdb/doc/stabs.texinfo 31 Oct 2006 22:38:27 -0000 1.19
+++ gdb/doc/stabs.texinfo 16 Jan 2007 21:19:52 -0000
@@ -1069,7 +1069,7 @@
plans to have the linker stop relocating stabs; I suspect that their the
debugger gets the address from the corresponding ELF (not stab) symbol.
I'm not sure how to find which symbol of that name is the right one.
-The clean way to do all this would be to have a the value of a symbol
+The clean way to do all this would be to have the value of a symbol
descriptor @samp{S} symbol be an offset relative to the start of the
file, just like everything else, but that introduces obvious
compatibility problems. For more information on linker stab relocation,
More information about the Gdb-patches
mailing list