From 7640fe7108a1c68bdee82ea6a44a2c2b6274569c Mon Sep 17 00:00:00 2001 From: David MacKenzie Date: Fri, 10 Sep 1993 13:36:07 +0000 Subject: [PATCH] fix a few typos --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index faa08863167..2eed8891ca9 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +Fri Sep 10 06:34:20 1993 David J. Mackenzie (djm@thepub.cygnus.com) + + * gdb.texinfo: Fix a few typos. + Wed Sep 8 09:11:52 1993 Jim Kingdon (kingdon@lioth.cygnus.com) * gdb.texinfo: Clarify how well it works with Fortran. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 4276722f968..aaddb7c9a85 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -3805,7 +3805,7 @@ The left operand of @samp{@@} must reside in memory. Array values made with @samp{@@} in this way behave just like other arrays in terms of subscripting, and are coerced to pointers when used in expressions. Artificial arrays most often appear in expressions via the value history -(@pxref{Value History, ,Value history}), after printing one out.) +(@pxref{Value History, ,Value history}), after printing one out. Sometimes the artificial array mechanism is not quite enough; in moderately complex data structures, the elements of interest may not @@ -4036,7 +4036,7 @@ each time your program stops. @xref{Expressions, ,Expressions}. @item display/@var{fmt} @var{exp} For @var{fmt} specifying only a display format and not a size or count, add the expression @var{exp} to the auto-display list but -arranges to display it each time in the specified format @var{fmt}. +arrange to display it each time in the specified format @var{fmt}. @xref{Output Formats,,Output formats}. @item display/@var{fmt} @var{addr} @@ -5202,7 +5202,7 @@ Address operator. Defined on variables. Same precedence as @code{++}. @ifclear CONLY For debugging C++, @value{GDBN} implements a use of @samp{&} beyond what is allowed in the C++ language itself: you can use @samp{&(&@var{ref})} -(or, if you prefer, simply @samp{&&@var{ref}} to examine the address +(or, if you prefer, simply @samp{&&@var{ref}}) to examine the address where a C++ reference variable (declared with @samp{&@var{ref}}) is stored. @end ifclear -- 2.30.2