* gdb.texinfo (Continuing and Stepping): Fixed markup and typos,
as suggested by Dmitry Sivachenko <dima@Chg.RU>.
This commit is contained in:
parent
5cec67bf93
commit
4a92d01105
2 changed files with 17 additions and 12 deletions
|
@ -1,3 +1,8 @@
|
|||
2000-11-19 Eli Zaretskii <eliz@is.elta.co.il>
|
||||
|
||||
* gdb.texinfo (Continuing and Stepping): Fixed markup and typos,
|
||||
as suggested by Dmitry Sivachenko <dima@Chg.RU>.
|
||||
|
||||
2000-11-10 Christopher Faylor <cgf@cygnus.com>
|
||||
|
||||
* gdb.texinfo: Document new 'set step-mode' command.
|
||||
|
|
|
@ -3281,12 +3281,12 @@ without debugging information, use the @code{stepi} command, described
|
|||
below.
|
||||
@end quotation
|
||||
|
||||
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
|
||||
function that has debugging information is called within the line.
|
||||
In other words, @code{step} @emph{steps inside} any functions called
|
||||
within the line.
|
||||
The @code{step} command only stops at the first instruction of a source
|
||||
line. This prevents the multiple stops that could otherwise occur in
|
||||
@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.
|
||||
|
||||
Also, the @code{step} command only enters a function if there is line
|
||||
number information for the function. Otherwise it acts like the
|
||||
|
@ -3321,23 +3321,23 @@ An argument @var{count} is a repeat count, as for @code{step}.
|
|||
|
||||
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 set step-mode
|
||||
@item set step-mode
|
||||
@cindex functions without line info, and stepping
|
||||
@cindex stepping into functions with no line info
|
||||
@itemx set step-mode on
|
||||
The @code{set step-mode on} command causes the @code{step} command to to
|
||||
The @code{set step-mode on} command causes the @code{step} command to
|
||||
stop at the first instruction of a function which contains no debug line
|
||||
information rather than stepping over it.
|
||||
|
||||
This is useful in cases where you may be interested in inspecting the assembly
|
||||
language of a function which has no symbolic info and do not want @value{GDBN}
|
||||
to automatically skip over this function.
|
||||
This is useful in cases where you may be interested in inspecting the
|
||||
machine instructions of a function which has no symbolic info and do not
|
||||
want @value{GDBN} to automatically skip over this function.
|
||||
|
||||
@item set step-mode off
|
||||
Causes the step command to step over any functions which contains no
|
||||
Causes the @code{step} command to step over any functions which contains no
|
||||
debug information. This is the default.
|
||||
|
||||
@kindex finish
|
||||
|
|
Loading…
Reference in a new issue