Patch to gdb.texinfo

[Dmitry Sivachenko]

Please apply this patch to gdb.texinfo (revision 1.1.1.14).
This fixes several typos and markup inconsistences.

Thank you in advance,
Dima.

--- gdb.1.1.1.14.texinfo	Wed Jan 26 15:56:12 2000
+++ gdb.texinfo	Wed Mar  8 15:39:22 2000
@@ -918,6 +918,7 @@
 @kindex quit @r{[}@var{expression}@r{]}
 @kindex q
 @item quit
+@item quit @r{[}@var{expression}@r{]}
 To exit @value{GDBN}, use the @code{quit} command (abbreviated @code{q}), or 
 type an end-of-file character (usually @kbd{C-d}).  If you do not supply 
 @var{expression}, @value{GDBN} will terminate normally; otherwise it will 
@@ -1114,7 +1115,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
@@ -1170,7 +1171,8 @@
 stack -- Examining the stack
 status -- Status inquiries
 support -- Support facilities
-tracepoints -- Tracing of program execution without stopping the program
+tracepoints -- Tracing of program execution without@*
+               stopping the program
 user-defined -- User-defined commands
 
 Type "help" followed by a class name for a list of 
@@ -1180,6 +1182,7 @@
 Command name abbreviations are allowed if unambiguous.
 (@value{GDBP})
 @end smallexample
+@c the above line break eliminates huge line overfull...
 
 @item help @var{class}
 Using one of the general help classes as an argument, you can get a
@@ -3199,6 +3202,7 @@
 @kindex stepi
 @kindex si
 @item stepi
+@itemx stepi @var{arg}
 @itemx si
 Execute one machine instruction, then stop and return to the debugger.
 
@@ -3213,6 +3217,7 @@
 @kindex nexti
 @kindex ni
 @item nexti
+@itemx nexti @var{arg}
 @itemx ni
 Execute one machine instruction, but if it is a function call,
 proceed until the function returns.
@@ -3254,6 +3259,7 @@
 @table @code
 @kindex info signals
 @item info signals
+@itemx info handle
 Print a table of all the kinds of signals and how @value{GDBN} has been told to
 handle each one.  You can use this to see the signal numbers of all
 the defined types of signals.
@@ -4004,7 +4010,7 @@
 @c FIXME: I think this example should also show the addresses in
 @c symbolic form, as they usually would be displayed.
 @smallexample
-(@value{GDBP}) info line m4_changecom
+(@value{GDBP}) info line m4_changequote
 Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350.
 @end smallexample
 
@@ -5375,7 +5381,7 @@
 @item .ch
 @itemx .c186
 @itemx .c286
-CHILL source file.
+CHILL source file
 
 @item .mod
 Modula-2 source file
@@ -5908,8 +5914,8 @@
 @samp{\n} for newline.
 
 @item
-String constants are a sequence of character constants surrounded
-by double quotes (@code{"}).
+String constants are a sequence of character constants (without
+single quotes) surrounded by double quotes (@code{"}).
 
 @item
 Pointer constants are an integral value.  You can also write pointers
@@ -6263,7 +6269,7 @@
 types.
 
 @item <=@r{, }>=
-Less than, greater than, less than or equal to, greater than or equal to
+Less than or equal to, greater than or equal to
 on integral, floating-point and enumerated types, or set inclusion on
 set types.  Same precedence as @code{<}.
 
@@ -7803,7 +7809,7 @@
 file has been loaded; @value{GDBN} cannot figure this out for itself.
 You can specify up to three addresses, in which case they are taken to be
 the addresses of the text, data, and bss segments respectively.
-For complicated cases, you can specify an arbitrary number of @r{-T}@var{section} @var{address}
+For complicated cases, you can specify an arbitrary number of @samp{@r{-T}@var{section} @var{address}}
 pairs, to give an explicit section name and base address for that section.
 You can specify any @var{address} as an expression.
 
@@ -7811,7 +7817,7 @@
 originally read with the @code{symbol-file} command.  You can use the
 @code{add-symbol-file} command any number of times; the new symbol data thus
 read keeps adding to the old.  To discard all old symbol data instead,
-use the @code{symbol-file} command.
+use the @code{symbol-file} command without arguments.
 
 @code{add-symbol-file} does not repeat if you press @key{RET} after using it.
 
@@ -9933,7 +9939,7 @@
 @noindent
 (Later, if you wish to return control to the DOS console, you can use
 the command @code{CTTY con}---but you must send it over the device that
-had control, in our example over the @file{COM1} serial line).
+had control, in our example over the @file{COM1} serial line.)
 
 From the Unix host, use a communications program such as @code{tip} or
 @code{cu} to communicate with the PC; for example,
@@ -10112,7 +10118,7 @@
 @kindex target sh3@r{, with H8/300}
 @kindex target sh3e@r{, with H8/300}
 @item target sh3 @var{dev}
-@item target sh3e @var{dev}
+@itemx target sh3e @var{dev}
 Hitachi SH-3 and SH-3E target systems.
 
 @end table
@@ -10157,14 +10163,14 @@
 @c only for Unix hosts
 @kindex device
 @cindex serial device, Hitachi micros
-Use the special @code{@value{GDBP}} command @samp{device @var{port}} if you
+Use the special @code{@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{GDBP}} has another special command to set the communications
+@code{@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,
@@ -10211,7 +10217,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{GDBP}} prompts
+the name of your program as the argument.  @code{@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