diff options
| -rw-r--r-- | gdb/doc/ChangeLog | 7 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 9 |
2 files changed, 15 insertions, 1 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 9358b19..e03b737 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,10 @@ +Fri Feb 4 06:31:31 1994 Jim Kingdon (kingdon@lioth.cygnus.com) + + * gdb.texinfo (Continuing and Stepping): When talking about "step" + versus functions without line numbers, also mention stepping into + them as well as "step" when you are in them. Tell the user how to + deal with the situation. Add comment about "debugging information". + Thu Feb 3 11:39:59 1994 Jim Kingdon (kingdon@lioth.cygnus.com) * stabs.texinfo (Enumerations): Document restriction on where diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index a1f9217..a902084 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2846,10 +2846,17 @@ line, then stop it and return control to @value{GDBN}. This command is abbreviated @code{s}. @quotation +@c "without debugging information" is imprecise; actually "without line +@c numbers in the debugging information". (gcc -g1 has debugging info but +@c not line numbers). But it seems complex to try to make that +@c distinction here. @emph{Warning:} If you use the @code{step} command while control is within a function that was compiled without debugging information, execution proceeds until control reaches a function that does have -debugging information. +debugging information. Likewise, it will not step into a function which +is compiled without debugging information. To step through functions +without debugging information, use the @code{stepi} command, described +below. @end quotation @item step @var{count} |