This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Changes to gdb.texinfo
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Changes to gdb.texinfo
- From: Dima Sivachenko <dima at Chg dot RU>
- Date: Sun, 10 Oct 1999 17:54:41 +0400 (MSD)
Hello!
1. In order to approve the existence of lines 3172 and 3182 of gdb.texinfo
(revision 1.1.1.9), you should probably add something like
'@r{[}@var{count}@r{]}' to the appropriate @item sections.
2. I think it is nessesary to apply the following patch for better
markup:
--- gdb.1.1.1.9.texinfo Sun Oct 10 13:04:30 1999
+++ gdb.1.1.1.9.new.texinfo Sun Oct 10 17:45:13 1999
@@ -3056,7 +3056,7 @@
The @code{step} command only stops at the first instruction of a
source line. This prevents the multiple stops that could otherwise occur in
-switch statements, for loops, etc. @code{step} continues to stop if a
+@code{switch} statements, @code{for} loops, etc. @code{step} continues to stop if a
function that has debugging information is called within the line.
In other words, @code{step} @emph{steps inside} any functions called
within the line.
@@ -3094,7 +3094,7 @@
The @code{next} command only stops at the first instruction of a
source line. This prevents multiple stops that could otherwise occur in
-switch statements, for loops, etc.
+@code{switch} statements, @code{for} loops, etc.
@kindex finish
@item finish
3. I don't understand the phrase 'code breakpoint' at the line 2434.
Please explain it to me or rewrite this sentence to make things clear.
Thank you in advance,
Dima.