aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--gdb/doc/gdb.texinfo2
-rw-r--r--gdb/doc/remote.texi4
2 files changed, 3 insertions, 3 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f3cf819..df5cc2a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -3392,7 +3392,7 @@ commands:
@cindex @code{heuristic-fence-post} (MIPS)
@table @code
@item set heuristic-fence-post @var{limit}
-Restrict @var{GDBN} to examining at most @var{limit} bytes in its search
+Restrict @value{GDBN} to examining at most @var{limit} bytes in its search
for the beginning of a function. A value of @code{0} (the default)
means there is no limit.
diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi
index 3f52a69..a1a75de 100644
--- a/gdb/doc/remote.texi
+++ b/gdb/doc/remote.texi
@@ -440,9 +440,9 @@ allows you to connect your program with a remote @value{GDBN} via
because it requires essentially the same operating-system facilities
that @value{GDBN} itself does. In fact, a system that can run
@code{gdbserver} to connect to a remote @value{GDBN} could also run
-@var{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
+@value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
because it is a much smaller program than @value{GDBN} itself. It is
-also easier to port than all of @var{GDBN}, so you may be able to get
+also easier to port than all of @value{GDBN}, so you may be able to get
started more quickly on a new system by using @code{gdbserver}.
@value{GDBN} and @code{gdbserver} communicate via either a serial line