This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
patch for gdb.texinfo
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: patch for gdb.texinfo
- From: Dmitry Sivachenko <dima at Chg dot RU>
- Date: Thu, 27 Jan 2000 23:09:57 +0300 (MSK)
Hello!
Please apply this patch to gdb.texinfo (I made it against revision 1.1.1.14).
It corrects several typos and adds better markup.
Thank you in advance,
Dima.
--- gdb.texinfo.orig Thu Jan 27 22:35:02 2000
+++ gdb.texinfo Thu Jan 27 23:06:45 2000
@@ -403,7 +403,7 @@
@b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
@b{baz}
-@b{C-d}
+@kbd{C-d}
m4: End of input: 0: fatal error: EOF in string
@end smallexample
@@ -620,7 +620,7 @@
lengths. We allow @code{m4} exit by giving it an EOF as input:
@smallexample
-@b{C-d}
+@kbd{C-d}
Program exited normally.
@end smallexample
@@ -697,7 +697,7 @@
will warn you if it is unable to attach or to read core dumps.
You can run @code{gdb} without printing the front material, which describes
-@value{GDBN}'s non-warranty, by specifying @code{-silent}:
+@value{GDBN}'s non-warranty, by specifying @option{-silent}:
@smallexample
@value{GDBP} -silent
@@ -720,7 +720,7 @@
All options and command line arguments you give are processed
in sequential order. The order makes a difference when the
-@samp{-x} option is used.
+@option{-x} option is used.
@menu
@@ -733,12 +733,12 @@
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} options respectively. (@value{GDBN} reads the first argument
+the same as if the arguments were specified by the @option{-se} and
+@option{-c} 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
+@option{-se} option followed by that argument; and the second argument
that does not have an associated option flag, if any, as equivalent to
-the @samp{-c} option followed by that argument.)
+the @option{-c} option followed by that argument.)
If @value{GDBN} has not been configured to included core file support,
such as for most embedded targets, then it will complain about a second
@@ -807,7 +807,7 @@
@end table
-You typically combine the @code{-mapped} and @code{-readnow} options in
+You typically combine the @option{-mapped} and @option{-readnow} options in
order to build a @file{.syms} file that contains complete symbol
information. (@xref{Files,,Commands to specify files}, for information
on @file{.syms} files.) A simple @value{GDBN} invocation to do nothing
@@ -839,8 +839,8 @@
@item -batch
Run in batch mode. Exit with status @code{0} after processing all the
-command files specified with @samp{-x} (and all commands from
-initialization files, if not inhibited with @samp{-n}). Exit with
+command files specified with @option{-x} (and all commands from
+initialization files, if not inhibited with @option{-n}). Exit with
nonzero status if an error occurs in executing the @value{GDBN} commands
in the command files.
@@ -947,7 +947,7 @@
@cindex shell escape
@item shell @var{command string}
Invoke a standard shell to execute @var{command string}.
-If it exists, the environment variable @code{SHELL} determines which
+If it exists, the environment variable @env{SHELL} determines which
shell to run. Otherwise @value{GDBN} uses the default shell
(@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.).
@end table
@@ -1114,7 +1114,7 @@
@kbd{M-?} to request word completion:
@example
-(@value{GDBP}) b 'bubble( @key{M-?}
+(@value{GDBP}) b 'bubble( @kbd{M-?}
bubble(double,double) bubble(int,int)
(@value{GDBP}) b 'bubble(
@end example
@@ -1290,7 +1290,7 @@
version of @value{GDBN} you are running; as @value{GDBN} evolves, new
commands are introduced, and old ones may wither away. Also, many
system vendors ship variant versions of @value{GDBN}, and there are
-variant versions of @value{GDBN} in GNU/Linux distributions as well.
+variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well.
The version number is the same as the one announced when you start
@value{GDBN}.
@@ -1340,35 +1340,35 @@
variable or function and the correspondence between source line numbers
and addresses in the executable code.
-To request debugging information, specify the @samp{-g} option when you run
+To request debugging information, specify the @option{-g} option when you run
the compiler.
-Many C compilers are unable to handle the @samp{-g} and @samp{-O}
+Many C compilers are unable to handle the @option{-g} and @option{-O}
options together. Using those compilers, you cannot generate optimized
executables containing debugging information.
-@value{NGCC}, the @sc{gnu} C compiler, supports @samp{-g} with or
-without @samp{-O}, making it possible to debug optimized code. We
-recommend that you @emph{always} use @samp{-g} whenever you compile a
+@value{NGCC}, the @sc{gnu} C compiler, supports @option{-g} with or
+without @option{-O}, making it possible to debug optimized code. We
+recommend that you @emph{always} use @option{-g} whenever you compile a
program. You may think your program is correct, but there is no sense
in pushing your luck.
@cindex optimized code, debugging
@cindex debugging optimized code
-When you debug a program compiled with @samp{-g -O}, remember that the
+When you debug a program compiled with @option{-g -O}, remember that the
optimizer is rearranging your code; the debugger shows you what is
really there. Do not be too surprised when the execution path does not
exactly match your source file! An extreme example: if you define a
variable, but never use it, @value{GDBN} never sees that
variable---because the compiler optimizes it out of existence.
-Some things do not work as well with @samp{-g -O} as with just
-@samp{-g}, particularly on machines with instruction scheduling. If in
-doubt, recompile with @samp{-g} alone, and if this fixes the problem,
+Some things do not work as well with @option{-g -O} as with just
+@option{-g}, particularly on machines with instruction scheduling. If in
+doubt, recompile with @option{-g} alone, and if this fixes the problem,
please report it to us as a bug (including a test case!).
Older versions of the @sc{gnu} C compiler permitted a variant option
-@w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this
+@w{@option{-gg}} for debugging information. @value{GDBN} no longer supports this
format; if your @sc{gnu} C compiler has this option, do not use it.
@need 2000
@@ -1409,7 +1409,7 @@
(such as wildcard expansion or variable substitution) in describing
the arguments.
In Unix systems, you can control which shell is used with the
-@code{SHELL} environment variable.
+@env{SHELL} environment variable.
@xref{Arguments, ,Your program's arguments}.
@item The @emph{environment.}
@@ -1456,8 +1456,8 @@
@code{run} command.
They are passed to a shell, which expands wildcard characters and
performs redirection of I/O, and thence to your program. Your
-@code{SHELL} environment variable (if it exists) specifies what shell
-@value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses
+@env{SHELL} environment variable (if it exists) specifies what shell
+@value{GDBN} uses. If you do not define @env{SHELL}, @value{GDBN} uses
the default shell (@file{/bin/sh} on Unix).
On non-Unix systems, the program is usually invoked directly by
@@ -1497,7 +1497,7 @@
@table @code
@kindex path
@item path @var{directory}
-Add @var{directory} to the front of the @code{PATH} environment variable
+Add @var{directory} to the front of the @env{PATH} environment variable
(the search path for executables), for both @value{GDBN} and your program.
You may specify several directory names, separated by whitespace or by a
system-dependent separator character (@samp{:} on Unix, @samp{;} on
@@ -1515,7 +1515,7 @@
@kindex show paths
@item show paths
-Display the list of search paths for executables (the @code{PATH}
+Display the list of search paths for executables (the @env{PATH}
environment variable).
@kindex show environment
@@ -1557,10 +1557,10 @@
@emph{Warning:} On Unix systems, @value{GDBN} runs your program using
the shell indicated
-by your @code{SHELL} environment variable if it exists (or
-@code{/bin/sh} if not). If your @code{SHELL} variable names a shell
+by your @env{SHELL} environment variable if it exists (or
+@code{/bin/sh} if not). If your @env{SHELL} variable names a shell
that runs an initialization file---such as @file{.cshrc} for C-shell, or
-@file{.bashrc} for BASH---any variables you set in that file affect
+@file{.bashrc} for Bash---any variables you set in that file affect
your program. You may wish to move setting of environment variables to
files that are only run when you sign on, such as @file{.login} or
@file{.profile}.
@@ -2996,7 +2996,7 @@
@item
Relink your program so that the text segment is nonsharable, using the
-linker option @samp{-N}. The operating system limitation may not apply
+linker option @option{-N}. The operating system limitation may not apply
to nonsharable executables.
@end enumerate
@c @end ifclear
@@ -3481,7 +3481,7 @@
@cindex frameless execution
Some compilers provide a way to compile functions so that they operate
without stack frames. (For example, the @code{@value{GCC}} option
-@samp{-fomit-frame-pointer} generates functions without a frame.)
+@option{-fomit-frame-pointer} generates functions without a frame.)
This is occasionally done with heavily used library functions to save
the frame setup time. @value{GDBN} has limited facilities for dealing
with these function invocations. If the innermost function invocation
@@ -3594,7 +3594,7 @@
addition, this can be useful when your program has multiple stacks and
switches between them.
-On the SPARC architecture, @code{frame} needs two addresses to
+On the @sc{sparc} architecture, @code{frame} needs two addresses to
select an arbitrary frame: a frame pointer and a stack pointer.
On the MIPS and Alpha architecture, it needs two addresses: a stack
@@ -4300,9 +4300,9 @@
To solve such problems, either recompile without optimizations, or use a
different debug info format, if the compiler supports several such
formats. For example, @value{NGCC}, the @sc{gnu} C/C++ compiler usually
-supports the @samp{-gstabs} option. @samp{-gstabs} produces debug info
+supports the @option{-gstabs} option. @option{-gstabs} produces debug info
in a format that is superior to formats such as COFF. You may be able
-to use DWARF-2 (@samp{-gdwarf-2}), which is also an effective form for
+to use DWARF-2 (@option{-gdwarf-2}), which is also an effective form for
debug info. See @ref{Debugging Options,,Options for Debugging Your
Program or @sc{gnu} CC, gcc.info, Using @sc{gnu} CC}, for more
information.
@@ -5238,7 +5238,7 @@
Whenever possible, these four standard register names are available on
your machine even though the machine has different canonical mnemonics,
so long as there is no conflict. The @code{info registers} command
-shows the canonical names. For example, on the SPARC, @code{info
+shows the canonical names. For example, on the @sc{sparc}, @code{info
registers} displays the processor status register as @code{$psr} but you
can also refer to it as @code{$ps}; and on x86-based machines @code{$ps}
is an alias for the @sc{eflags} register.
@@ -5691,7 +5691,7 @@
For best results when using @sc{gnu} C++, use the stabs debugging
format. You can select that format explicitly with the @code{g++}
-command-line options @samp{-gstabs} or @samp{-gstabs+}. See
+command-line options @option{-gstabs} or @option{-gstabs+}. See
@ref{Debugging Options,,Options for Debugging Your Program or @sc{gnu}
CC, gcc.info, Using @sc{gnu} CC}, for more information.
@@ -5954,7 +5954,7 @@
special support. In particular, if your compiler generates a.out, MIPS
@sc{ecoff}, RS/6000 @sc{xcoff}, or @sc{elf} with stabs extensions to the
symbol table, these facilities are all available. (With @sc{gnu} CC,
-you can use the @samp{-gstabs} option to request stabs debugging
+you can use the @option{-gstabs} option to request stabs debugging
extensions explicitly.) Where the object code format is standard
@sc{coff} or @sc{dwarf} in @sc{elf}, on the other hand, most of the C++
support in @value{GDBN} does @emph{not} work.
@@ -6620,7 +6620,7 @@
The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available
with any language, is not useful with Modula-2. Its
-intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be
+intent is to aid the debugging of dynamic arrays, which cannot be
created in Modula-2 as they can in C or C++. However, because an
address can be specified by an integral constant, the construct
@samp{@{@var{type}@}@var{adrexp}} is still useful.
@@ -6704,10 +6704,10 @@
@item @r{@emph{Procedure mode}}
The procedure mode is displayed by @code{type = PROC(<parameter list>)
-<return mode> EXCEPTIONS (<exception list>)}. The @code{<parameter
+<return mode> EXCEPTIONS (<exception list>)}. The @code{<parameter
list>} is a list of the parameter modes. @code{<return mode>} indicates
-the mode of the result of the procedure if any. The exceptionlist lists
-all possible exceptions which can be raised by the procedure.
+the mode of the result of the procedure if any. The @code{<exception list>}
+lists all possible exceptions which can be raised by the procedure.
@ignore
@item @r{@emph{Instance mode}}
@@ -6762,7 +6762,7 @@
list>)}. The @code{<field list>} consists of names and modes of fields
of the structure. Variant structures have the keyword @code{CASE <field>
OF <variant fields> ESAC} in their field list. Since the current version
-of the GNU Chill compiler doesn't implement tag processing (no runtime
+of the @sc{gnu} Chill compiler doesn't implement tag processing (no runtime
checks of variant fields, and therefore no debugging info), the output
always displays all variant fields.
@smallexample
@@ -7002,7 +7002,7 @@
@item @code{SQRT()}
@end table
-For a detailed description refer to the GNU Chill implementation manual
+For a detailed description refer to the @sc{gnu} Chill implementation manual
chapter 1.6.
@end ignore
@@ -7660,7 +7660,7 @@
symbols and for the contents of pure memory. It is also the program
executed when you use the @code{run} command. If you do not specify a
directory and the file is not found in the @value{GDBN} working directory,
-@value{GDBN} uses the environment variable @code{PATH} as a list of
+@value{GDBN} uses the environment variable @env{PATH} as a list of
directories to search, just as the shell does when looking for a program
to run. You can change the value of this variable, for both @value{GDBN}
and your program, using the @code{path} command.
@@ -7669,7 +7669,7 @@
@file{@var{filename}.syms} may hold symbol table information for
@var{filename}. If so, @value{GDBN} maps in the symbol table from
@file{@var{filename}.syms}, starting up more quickly. See the
-descriptions of the file options @samp{-mapped} and @samp{-readnow}
+descriptions of the file options @option{-mapped} and @option{-readnow}
(available on the command line, and with the commands @code{file},
@code{symbol-file}, or @code{add-symbol-file}, described below),
for more information.
@@ -7681,13 +7681,13 @@
@kindex exec-file
@item exec-file @r{[} @var{filename} @r{]}
Specify that the program to be run (but not the symbol table) is found
-in @var{filename}. @value{GDBN} searches the environment variable @code{PATH}
+in @var{filename}. @value{GDBN} searches the environment variable @env{PATH}
if necessary to locate your program. Omitting @var{filename} means to
discard information on the executable file.
@kindex symbol-file
@item symbol-file @r{[} @var{filename} @r{]}
-Read symbol table information from file @var{filename}. @code{PATH} is
+Read symbol table information from file @var{filename}. @env{PATH} is
searched when necessary. Use the @code{file} command to get both symbol
table and program to run from the same file.
@@ -7739,18 +7739,18 @@
@item symbol-file @var{filename} @r{[} -readnow @r{]} @r{[} -mapped @r{]}
@itemx file @var{filename} @r{[} -readnow @r{]} @r{[} -mapped @r{]}
You can override the @value{GDBN} two-stage strategy for reading symbol
-tables by using the @samp{-readnow} option with any of the commands that
+tables by using the @option{-readnow} option with any of the commands that
load symbol table information, if you want to be sure @value{GDBN} has the
entire symbol table available.
If memory-mapped files are available on your system through the
-@code{mmap} system call, you can use another option, @samp{-mapped}, to
+@code{mmap} system call, you can use another option, @option{-mapped}, to
cause @value{GDBN} to write the symbols for your program into a reusable
file. Future @value{GDBN} debugging sessions map in symbol information
from this auxiliary symbol file (if the program has not changed), rather
than spending time reading the symbol table from the executable
-program. Using the @samp{-mapped} option has the same effect as
-starting @value{GDBN} with the @samp{-mapped} command-line option.
+program. Using the @option{-mapped} option has the same effect as
+starting @value{GDBN} with the @option{-mapped} command-line option.
You can use both options together, to make sure the auxiliary symbol
file has all the symbol information for your program.
@@ -7815,7 +7815,7 @@
@code{add-symbol-file} does not repeat if you press @key{RET} after using it.
-You can use the @samp{-mapped} and @samp{-readnow} options just as with
+You can use the @option{-mapped} and @option{-readnow} options just as with
the @code{symbol-file} command, to change how @value{GDBN} manages the symbol
table information for @var{filename}.
@@ -7828,10 +7828,10 @@
@kindex section
@item section
-The @code{section} command changes the base address of section SECTION of
-the exec file to ADDR. This can be used if the exec file does not contain
-section addresses, (such as in the a.out format), or when the addresses
-specified in the file itself are wrong. Each section must be changed
+The @code{section} command changes the base address of section @var{section} of
+the executable file to @var{address}. This can be used if the exec file does
+not contain section addresses, (such as in the a.out format), or when the
+addresses specified in the file itself are wrong. Each section must be changed
separately. The @code{info files} command, described below, lists all
the sections and their addresses.
@@ -7860,7 +7860,7 @@
when you use the @code{run} command, or when you examine a core file.
(Before you issue the @code{run} command, @value{GDBN} does not understand
references to a function in a shared library, however---unless you are
-debugging a core file).
+debugging a core file.)
On HP-UX, if the program loads a library explicitly, @value{GDBN}
automatically loads the symbols at the time of the @code{shl_load} call.
@@ -8043,7 +8043,7 @@
start a process and inspect its activity without abandoning your work on
a core file.
-For example, if you execute @samp{gdb a.out}, then the executable file
+For example, if you execute @samp{@value{GDBP} a.out}, then the executable file
@code{a.out} is the only active target. If you designate a core file as
well---presumably from a prior run that crashed and coredumped---then
@value{GDBN} has two active targets and uses them in tandem, looking
@@ -8186,7 +8186,7 @@
If your @value{GDBN} does not have a @code{load} command, attempting to
execute it gets the error message ``@code{You can't do that when your
-target is @dots{}}''
+target is @dots{}}''.
The file is loaded at whatever address is specified in the executable.
For some object file formats, you can specify the load address when you
@@ -8300,7 +8300,7 @@
@item On the target,
you must link with your program a few special-purpose subroutines that
implement the @value{GDBN} remote serial protocol. The file containing these
-subroutines is called a @dfn{debugging stub}.
+subroutines is called a @dfn{debugging stub}.
On certain remote targets, you can use an auxiliary program
@code{gdbserver} instead of linking a stub into your program.
@@ -8495,7 +8495,7 @@
either obtain it from your hardware manufacturer, or write your own.
@end table
-If you do not use the GNU C compiler, you may need other standard
+If you do not use the @sc{gnu} C compiler, you may need other standard
library subroutines as well; this varies from one stub to another,
but in general the stubs are likely to use any of the common library
subroutines which @code{@value{GCC}} generates as inline code.
@@ -9426,7 +9426,7 @@
you need an unstripped copy of your program, since @value{GDBN} needs
symbols and debugging information. Start up @value{GDBN} as usual,
using the name of the local copy of your program as the first argument.
-(You may also need the @w{@samp{--baud}} option if the serial line is
+(You may also need the @w{@option{--baud}} option if the serial line is
running at anything other than 9600@dmn{bps}.) After that, use @code{target
remote} to establish communications with @code{gdbserver}. Its argument
is either a device name (usually a serial device, like
@@ -9495,7 +9495,7 @@
you need an unstripped copy of your program, since @value{GDBN} needs
symbols and debugging information. Start up @value{GDBN} as usual,
using the name of the local copy of your program as the first argument.
-(You may also need the @w{@samp{--baud}} option if the serial line is
+(You may also need the @w{@option{--baud}} option if the serial line is
running at anything other than 9600@dmn{bps}. After that, use @code{target
remote} to establish communications with @code{gdbserve.nlm}. Its
argument is a device name (usually a serial device, like
@@ -9880,7 +9880,7 @@
@var{keyword} is an entry in the AMD configuration file @file{udi_soc}.
This file contains keyword entries which specify parameters used to
connect to a29k targets. If the @file{udi_soc} file is not in your
-working directory, you must set the environment variable @samp{UDICONF}
+working directory, you must set the environment variable @env{UDICONF}
to its pathname.
@end table
@@ -10410,7 +10410,7 @@
target architecture.
@quotation
-@emph{Warning:} if you specify @samp{-O}, but are actually trying to
+@emph{Warning:} if you specify @option{-O}, but are actually trying to
connect to a target system that expects the newer protocol, the connection
fails, appearing to be a speed mismatch. @value{GDBN} repeatedly
attempts to reconnect at several different line speeds. You can abort
@@ -10427,7 +10427,7 @@
@end quotation
@end table
-The standard @samp{-b} option controls the line speed used on the serial
+The standard @option{-b} option controls the line speed used on the serial
port.
@c @group
@@ -10740,10 +10740,10 @@
@end table
@kindex Compiling
-When compiling for debugging, include the options @samp{-g} to get debug
+When compiling for debugging, include the options @option{-g} to get debug
information and @samp{-Ttext} to relocate the program to where you wish to
-load it on the target. You may also want to add the options @samp{-n} or
-@samp{-N} in order to reduce the size of the sections. Example:
+load it on the target. You may also want to add the options @option{-n} or
+@option{-N} in order to reduce the size of the sections. Example:
@example
sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N
@@ -11153,7 +11153,7 @@
list, and where it writes the command history from this session when it
exits. You can access this list through history expansion or through
the history command editing characters listed below. This file defaults
-to the value of the environment variable @code{GDBHISTFILE}, or to
+to the value of the environment variable @env{GDBHISTFILE}, or to
@file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable
is not set.
@@ -11172,7 +11172,7 @@
@item set history size @var{size}
Set the number of commands which @value{GDBN} keeps in its history list.
This defaults to the value of the environment variable
-@code{HISTSIZE}, or to 256 if this variable is not set.
+@env{HISTSIZE}, or to 256 if this variable is not set.
@end table
@cindex history expansion
@@ -11247,7 +11247,7 @@
Normally @value{GDBN} knows the size of the screen from the terminal
driver software. For example, on Unix @value{GDBN} uses the termcap data base
-together with the value of the @code{TERM} environment variable and the
+together with the value of the @env{TERM} environment variable and the
@code{stty rows} and @code{stty cols} settings. If this is not correct,
you can override it with the @code{set height} and @code{set
width} commands:
@@ -11566,13 +11566,15 @@
@dfn{init files}. These are files named @file{.gdbinit} on Unix, or
@file{gdb.ini} on DOS/Windows. @value{GDBN} reads the init file (if
any) in your home directory@footnote{On DOS/Windows systems, the home
-directory is the one pointed to by the @code{HOME} environment
+directory is the one pointed to by the @env{HOME} environment
variable.}, then processes command line options and operands, and then
reads the init file (if any) in the current working directory. This is
so the init file in your home directory can set options (such as
@code{set complaints}) which affect the processing of the command line
options and operands. The init files are not executed if you use the
-@samp{-nx} option; @pxref{Mode Options, ,Choosing modes}.
+@option{-nx} option
+(@pxref{Mode Options, ,Choosing modes}).
+@comment pxref should be used only in () !!
@cindex init file name
On some configurations of @value{GDBN}, the init file is known by a
@@ -11584,15 +11586,15 @@
@kindex .vxgdbinit
@itemize @bullet
@item
-VxWorks (Wind River Systems real-time OS): @samp{.vxgdbinit}
+VxWorks (Wind River Systems real-time OS): @file{.vxgdbinit}
@kindex .os68gdbinit
@item
-OS68K (Enea Data Systems real-time OS): @samp{.os68gdbinit}
+OS68K (Enea Data Systems real-time OS): @file{.os68gdbinit}
@kindex .esgdbinit
@item
-ES-1800 (Ericsson Telecom AB M68000 emulator): @samp{.esgdbinit}
+ES-1800 (Ericsson Telecom AB M68000 emulator): @file{.esgdbinit}
@end itemize
You can also request the execution of a command file with the
@@ -11747,7 +11749,7 @@
current directory, it can be easy to confuse Emacs about the location of
the source files, in which case the auxiliary display buffer does not
appear to show your source. @value{GDBN} can find programs by searching your
-environment's @code{PATH} variable, so the @value{GDBN} input and output
+environment's @env{PATH} variable, so the @value{GDBN} input and output
session proceeds normally; but Emacs does not get enough information
back from @value{GDBN} to locate the source files in this situation. To
avoid this problem, either start @value{GDBN} mode from the directory where
@@ -11934,7 +11936,7 @@
@c should add a web page ref...
In any event, we also recommend that you send bug reports for
-@value{GDBN} to this addresses:
+@value{GDBN} to this address:
@example
bug-gdb@@gnu.org
@@ -12010,13 +12012,13 @@
@item
What compiler (and its version) was used to compile the program you are
debugging---e.g. ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP
-C Compiler''. For GCC, you can say @code{gcc --version} to get this
+C Compiler''. For @value{NGCC}, you can say @code{gcc --version} to get this
information; for other compilers, see the documentation for those
compilers.
@item
The command arguments you gave the compiler to compile your example and
-observe the bug. For example, did you use @samp{-O}? To guarantee
+observe the bug. For example, did you use @option{-O}? To guarantee
you will not omit something important, list them all. A copy of the
Makefile (or the output from make) is sufficient.
@@ -12183,7 +12185,7 @@
@TeX{} also requires a macro definitions file called
@file{texinfo.tex}. This file tells @TeX{} how to typeset a document
written in Texinfo format. On its own, @TeX{} cannot either read or
-typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB
+typeset a Texinfo file. @file{texinfo.tex} is distributed with @value{GDBN}
and is located in the @file{gdb-@var{version-number}/texinfo}
directory.
@@ -12290,7 +12292,7 @@
directories for multiple libraries or programs, such as the
@file{gdb-@value{GDBVN}} source directory for version @value{GDBVN}, @code{configure}
creates configuration files for every directory level underneath (unless
-you tell it not to, with the @samp{--norecursion} option).
+you tell it not to, with the @option{--norecursion} option).
You can run the @code{configure} script from any of the
subordinate directories in the @value{GDBN} distribution if you only want to
@@ -12308,7 +12310,7 @@
You can install @code{@value{GDBP}} anywhere; it has no hardwired paths.
However, you should make sure that the shell on your path (named by
-the @samp{SHELL} environment variable) is publicly readable. Remember
+the @env{SHELL} environment variable) is publicly readable. Remember
that @value{GDBN} uses the shell to start your program---some systems refuse to
let @value{GDBN} debug child processes whose programs are not readable.
@@ -12331,11 +12333,11 @@
program specified there.
To build @code{gdb} in a separate directory, run @code{configure}
-with the @samp{--srcdir} option to specify where to find the source.
+with the @option{--srcdir} option to specify where to find the source.
(You also need to specify a path to find @code{configure}
itself from your working directory. If the path to @code{configure}
-would be the same as the argument to @samp{--srcdir}, you can leave out
-the @samp{--srcdir} option; it is assumed.)
+would be the same as the argument to @option{--srcdir}, you can leave out
+the @option{--srcdir} option; it is assumed.)
For example, with version @value{GDBVN}, you can build @value{GDBN} in a
separate directory for a Sun 4 like this: