* Patch for docs
2001-06-16 5:22 Patch for docs Dmitry Sivachenko
@ 2001-06-16 5:49 ` Dmitry Sivachenko
2001-06-17 0:01 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Sivachenko @ 2001-06-16 5:49 UTC (permalink / raw)
To: gdb-patches
On Sat, Jun 16, 2001 at 04:15:00PM +0400, Dmitry Sivachenko wrote:
> Hello!
>
> Please apply this patch to gdb.texinfo and annotate.texi.
>
> It fixes minor markup ussues.
>
> Thank you in advance,
> Dima.
I am sorry, forgot to attach the patch.
Here it is:
Index: annotate.texi
===================================================================
RCS file: /home/cvs/en-gdbman/annotate.texi,v
retrieving revision 1.2
diff -u -r1.2 annotate.texi
--- annotate.texi 2000/07/08 16:00:40 1.2
+++ annotate.texi 2001/06/16 12:11:58
@@ -167,6 +167,7 @@
^Z^Zvalue-history-end
@end smallexample
+@noindent
where @var{history-number} is the number it is getting in the value
history, @var{history-string} is a string, such as @samp{$5 = }, which
introduces the value to the user, @var{the-value} is the output
@@ -201,6 +202,7 @@
^Z^Zarg-end
@end smallexample
+@noindent
where @var{argument-name} is the name of the argument,
@var{separator-string} is text which separates the name from the value
for the user's benefit (such as @samp{=}), and @var{value-flags} and
@@ -223,6 +225,7 @@
^Z^Zfield-end
@end smallexample
+@noindent
where @var{field-name} is the name of the field, @var{separator-string}
is text which separates the name from the value for the user's benefit
(such as @samp{=}), and @var{value-flags} and @var{the-value} have the
@@ -234,6 +237,7 @@
^Z^Zarray-section-begin @var{array-index} @var{value-flags}
@end smallexample
+@noindent
where @var{array-index} is the index of the first element being
annotated and @var{value-flags} has the same meaning as in a
@code{value-history-begin} annotation. This is followed by any number
@@ -289,6 +293,7 @@
@var{level-string}
@end smallexample
+@noindent
where @var{level} is the number of the frame (0 is the innermost frame,
and other frames have positive numbers), @var{address} is the address of
the code executing in that frame, and @var{level-string} is a string
@@ -437,6 +442,7 @@
^Z^Zdisplay-end
@end smallexample
+@noindent
where @var{number} is the number of the display, @var{number-separator}
is intended to separate the number from what follows for the user,
@var{format} includes information such as the size, format, or other
@@ -559,6 +565,7 @@
^Z^Zbreakpoints-table
@end smallexample
+@noindent
where @var{header-entry} has the same syntax as an entry (see below) but
instead of containing data, it contains strings which are intended to
convey the meaning of each field to the user. This is followed by any
@@ -672,6 +679,7 @@
@var{end-text}
@end smallexample
+@noindent
where @var{name} is the name of the signal, such as @code{SIGILL} or
@code{SIGSEGV}, and @var{string} is the explanation of the signal, such
as @code{Illegal Instruction} or @code{Segmentation fault}.
Index: gdb.texinfo
===================================================================
RCS file: /home/cvs/en-gdbman/gdb.texinfo,v
retrieving revision 1.6
diff -u -r1.6 gdb.texinfo
--- gdb.texinfo 2000/11/19 13:39:41 1.6
+++ gdb.texinfo 2001/06/16 12:08:42
@@ -6552,9 +6552,10 @@
@code{<=}, and @code{>=} on sets as an error.
@end quotation
-@cindex Modula-2 built-ins
+
@node Built-In Func/Proc
@subsubsection Built-in functions and procedures
+@cindex Modula-2 built-ins
Modula-2 also makes available several built-in procedures and functions.
In describing these, the following metavariables are used:
^ permalink raw reply [flat|nested] 3+ messages in thread