gdb.texinfo: cosmetique

[Dmitry Sivachenko <dima at Chg dot RU>]

--- gdb.1.4.texinfo	Wed Mar 22 22:55:21 2000
+++ gdb.1.4.texinfo.new	Sun Mar 26 19:43:23 2000
@@ -1195,7 +1195,7 @@
 command.
 
 If you just want to see the list of alternatives in the first place, you
-can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?}
+can press @kbd{M-?} rather than pressing @key{TAB} twice.  @kbd{M-?}
 means @kbd{@key{META} ?}.  You can type this either by holding down a
 key designated as the @key{META} shift on your keyboard (if there is
 one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}.
@@ -1277,7 +1277,7 @@
 stack -- Examining the stack
 status -- Status inquiries
 support -- Support facilities
-tracepoints -- Tracing of program execution without@*
+tracepoints -- Tracing of program execution without
                stopping the program
 user-defined -- User-defined commands
 
@@ -2860,7 +2860,7 @@
 Break conditions can have side effects, and may even call functions in
 your program.  This can be useful, for example, to activate functions
 that log program progress, or to use your own print functions to
-format special data structures. The effects are completely predictable
+format special data structures.  The effects are completely predictable
 unless there is another enabled breakpoint at the same address.  (In
 that case, @value{GDBN} might see the other breakpoint first and stop your
 program without checking the condition of this one.)  Note that
@@ -3537,7 +3537,7 @@
 particular, whenever you ask @value{GDBN} for the value of a variable in
 your program, the value is found in the selected frame.  There are
 special @value{GDBN} commands to select whichever frame you are
-interested in. @xref{Selection, ,Selecting a frame}.
+interested in.  @xref{Selection, ,Selecting a frame}.
 
 When your program stops, @value{GDBN} automatically selects the
 currently executing frame and describes it briefly, similar to the 
@@ -6418,7 +6418,7 @@
 precedence as @code{*}.
 
 @item -
-Negative. Defined on @code{INTEGER} and @code{REAL} data.
+Negative.  Defined on @code{INTEGER} and @code{REAL} data.
 
 @item ^
 Pointer dereferencing.  Defined on pointer types.
@@ -6771,7 +6771,7 @@
 
 The Chill Datatype- (Mode) support of @value{GDBN} is directly related
 with the functionality of the @sc{gnu} Chill compiler, and therefore deviates
-slightly from the standard specification of the Chill language. The
+slightly from the standard specification of the Chill language.  The
 provided modes are:
 
 @c FIXME: this @table's contents effectively disable @code by using @r
@@ -6819,9 +6819,9 @@
 
 @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
+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
@@ -6877,7 +6877,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
@@ -6951,7 +6951,7 @@
 braces (@samp{@{@}}).  Fields enclosed by @samp{@{,@}} are residing
 on the same memory location and represent the current values of the
 memory location in their specific modes.  Since no tag processing is done
-all variants are displayed. A variant field is printed by
+all variants are displayed.  A variant field is printed by
 @code{(<variant name>) = .<field name>: <value>}.  (who implements the
 stuff ???)
 @smallexample
@@ -7067,7 +7067,7 @@
 An array slice is specified by @code{<array value>(<slice spec>)}, where
 @code{<slice spec>} can be either a range specified by expressions or by
 @code{<start expr> up <size>}.  @code{<size>} denotes the number of
-arrayelements the slice contains.  The delivered value is an array value
+array elements the slice contains.  The delivered value is an array value
 which is part of the specified array.
 
 @item Structure Field Values
@@ -7117,7 +7117,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
 
@@ -8250,7 +8250,7 @@
 @item target remote @var{dev}
 Remote serial target in GDB-specific protocol.  The argument @var{dev}
 specifies what serial device to use for the connection (e.g.
-@file{/dev/ttya}). @xref{Remote, ,Remote debugging}.  @code{target remote}
+@file{/dev/ttya}).  @xref{Remote, ,Remote debugging}.  @code{target remote}
 supports the @code{load} command.  This is only useful if you have
 some other way of getting the stub to the target system, and you can put
 it somewhere in memory where it won't get clobbered by the download.
@@ -8611,7 +8611,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.
@@ -8652,7 +8652,7 @@
 @noindent
 but if before calling @code{set_debug_traps}, you set it to point to a
 function in your program; that function is called when
-@code{@value{GDBN}} continues after stopping on a trap (for example, bus
+@value{GDBN} continues after stopping on a trap (for example, bus
 error).  The function indicated by @code{exceptionHook} is called with
 one parameter: an @code{int} which is the exception number.
 
@@ -8802,7 +8802,7 @@
 
 @var{packet-data} consists of a sequence of characters with the
 exception of @samp{#} and @samp{$} (see @samp{X} packet for an
-exception). @samp{:} can not appear as the third character in a packet.
+exception).  @samp{:} can not appear as the third character in a packet.
 Fields within the packet should be separated using @samp{,} and @samp{;}
 (unfortunately some packets chose to use @samp{:}).  Except where
 otherwise noted all numbers are represented in HEX with leading zeros
@@ -8872,7 +8872,7 @@
 @item set program arguments @strong{(reserved)} @emph{(optional)}
 @tab @code{A}@var{arglen}@code{,}@var{argnum}@code{,}@var{arg}@code{,...}
 @tab
-Initialized @samp{argv[]} array passed into program. @var{arglen}
+Initialized @samp{argv[]} array passed into program.  @var{arglen}
 specifies the number of bytes in the hex encoded byte stream @var{arg}.
 See @file{gdbserver} for more details.
 @item
@@ -8883,15 +8883,16 @@
 @item set baud @strong{(deprecated)}
 @tab @code{b}@var{baud}
 @tab
-Change the serial line speed to @var{baud}.  JTC: @emph{When does the
-transport layer state change?  When it's received, or after the ACK is
-transmitted.  In either case, there are problems if the command or the
-acknowledgment packet is dropped.} Stan: @emph{If people really wanted
-to add something like this, and get it working for the first time, they
-ought to modify ser-unix.c to send some kind of out-of-band message to a
-specially-setup stub and have the switch happen "in between" packets, so
-that from remote protocol's point of view, nothing actually
-happened.}
+Change the serial line speed to @var{baud}.
+@c JTC: @emph{When does the
+@c transport layer state change?  When it's received, or after the ACK is
+@c transmitted.  In either case, there are problems if the command or the
+@c acknowledgment packet is dropped.} Stan: @emph{If people really wanted
+@c to add something like this, and get it working for the first time, they
+@c ought to modify ser-unix.c to send some kind of out-of-band message to a
+@c specially-setup stub and have the switch happen "in between" packets, so
+@c that from remote protocol's point of view, nothing actually
+@c happened.}
 
 @item set breakpoint @strong{(deprecated)}
 @tab @code{B}@var{addr},@var{mode}
@@ -8903,7 +8904,7 @@
 @item continue
 @tab @code{c}@var{addr}
 @tab
-@var{addr} is address to resume. If @var{addr} is omitted, resume at
+@var{addr} is address to resume.  If @var{addr} is omitted, resume at
 current address.
 @item
 @tab reply
@@ -9048,14 +9049,14 @@
 @tab
 Read @var{length} bytes of memory starting at address @var{addr}.
 Neither @value{GDBN} nor the stub assume that sized memory transfers are assumed
-using word alligned accesses. FIXME: @emph{A word aligned memory
+using word alligned accesses.  FIXME: @emph{A word aligned memory
 transfer mechanism is needed.}
 @item
 @tab reply @var{XX...}
 @tab
-@var{XX...} is mem contents. Can be fewer bytes than requested if able
+@var{XX...} is mem contents.  Can be fewer bytes than requested if able
 to read only part of the data.  Neither @value{GDBN} nor the stub assume that
-sized memory transfers are assumed using word alligned accesses. FIXME:
+sized memory transfers are assumed using word alligned accesses.  FIXME:
 @emph{A word aligned memory transfer mechanism is needed.}
 @item
 @tab reply @code{E}@var{NN}
@@ -9605,7 +9606,7 @@
 the baud rate used by the connection.  @var{port} and @var{node} default
 to 0, @var{baud} defaults to 9600@dmn{bps}.
 
-For example, to debug Emacs with the argument @samp{foo.txt}and
+For example, to debug Emacs with the argument @samp{foo.txt} and
 communicate with @value{GDBN} over serial port number 2 or board 1 
 using a 19200@dmn{bps} connection:
 
@@ -9618,7 +9619,7 @@
 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
-running at anything other than 9600@dmn{bps}.  After that, use @code{target
+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
 @file{/dev/ttyb}).  For example:
@@ -9796,7 +9797,7 @@
 @item VxWorks-timeout @var{args}
 @kindex vxworks-timeout
 All VxWorks-based targets now support the option @code{vxworks-timeout}.  
-This option is set by the user, and  @var{args} represents the number of 
+This option is set by the user, and @var{args} represents the number of 
 seconds @value{GDBN} waits for responses to rpc's.  You might use this if 
 your VxWorks target is a slow software simulator or is on the far side 
 of a thin network line.
@@ -10279,14 +10280,14 @@
 @c only for Unix hosts
 @kindex device
 @cindex serial device, Hitachi micros
-Use the special @code{@value{GDBN}} command @samp{device @var{port}} if you
+Use the special @value{GDBN} command @samp{device @var{port}} if you
 need to explicitly set the serial device.  The default @var{port} is the
 first available port on your host.  This is only necessary on Unix
 hosts, where it is typically something like @file{/dev/ttya}.
 
 @kindex speed
 @cindex serial line speed, Hitachi micros
-@code{@value{GDBN}} has another special command to set the communications
+@value{GDBN} has another special command to set the communications
 speed: @samp{speed @var{bps}}.  This command also is only used from Unix
 hosts; on DOS hosts, set the line speed as usual from outside @value{GDBN} with
 the DOS @code{mode} command (for instance,
@@ -10333,7 +10334,7 @@
 @kindex target hms@r{, and serial protocol}
 Now that serial communications are set up, and the development board is
 connected, you can start up @value{GDBN}.  Call @code{@value{GDBP}} with
-the name of your program as the argument.  @code{@value{GDBN}} prompts
+the name of your program as the argument.  @value{GDBN} prompts
 you, as usual, with the prompt @samp{(@value{GDBP})}.  Use two special
 commands to begin your debugging session: @samp{target hms} to specify
 cross-debugging to the Hitachi board, and the @code{load} command to
@@ -10581,7 +10582,7 @@
 @subsection M68k
 
 The Motorola m68k configuration includes ColdFire support, and
-target command for the following ROM monitors.
+@code{target} command for the following ROM monitors.
 
 @table @code
 
@@ -10618,7 +10619,7 @@
 
 @end table
 
-[context?]
+@c [context?]
 
 @table @code
 
@@ -10700,7 +10701,6 @@
 
 @end table
 
-
 @noindent
 @value{GDBN} also supports these special commands for MIPS targets:
 
@@ -10857,7 +10857,7 @@
 @item timeout @var{args}
 @kindex remotetimeout
 @value{GDBN} supports the option @code{remotetimeout}.  
-This option is set by the user, and  @var{args} represents the number of 
+This option is set by the user, and @var{args} represents the number of 
 seconds @value{GDBN} waits for responses.  
 @end table
 
@@ -11304,7 +11304,7 @@
 @end ifset
 
 Since @kbd{!} is also the logical not operator in C, history expansion
-is off by default. If you decide to enable history expansion with the
+is off by default.  If you decide to enable history expansion with the
 @code{set history expansion on} command, you may sometimes need to
 follow @kbd{!} (when it is used as logical not, in an expression) with
 a space or a tab to prevent it from being expanded.  The readline