mirrors/binutils-gdb
1
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-24 10:35:12 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdb.texinfo (Tracepoint Actions): Mention the "info scope"

Browse Source 
command and provide a cross-reference to its description.
	(Symbols): Note that "info scope" is useful for trace experiments.
This commit is contained in:
Eli Zaretskii 2001-04-02 08:58:19 +00:00
parent dec0cb0ce3
commit f5c37c66ad
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/doc/ChangeLog
View File

@ -1,3 +1,9 @@
2001-04-02 Eli Zaretskii <eliz@is.elta.co.il>
* gdb.texinfo (Tracepoint Actions): Mention the "info scope"
command and provide a cross-reference to its description.
(Symbols): Note that "info scope" is useful for trace experiments.
2001-04-01 Eli Zaretskii <eliz@is.elta.co.il>
* gdb.texinfo (Symbols): Document "info scope".

8
gdb/doc/gdb.texinfo
View File

@ -5897,6 +5897,9 @@ You can give several consecutive @code{collect} commands, each one
with a single argument, or one @code{collect} command with several
arguments separated by commas: the effect is the same.
The command @code{info scope} (@pxref{Symbols, info scope}) is
particularly useful for figuring out what data to collect.
@kindex while-stepping @r{(tracepoints)}
@item while-stepping @var{n}
Perform @var{n} single-step traces after the tracepoint, collecting
@ -8246,6 +8249,11 @@ Symbol nline is a local variable in register $edx, length 4.
Symbol repeat is a local variable at frame offset -8, length 4.
@end smallexample
@noindent
This command is especially useful for determining what data to collect
during a @dfn{trace experiment}, see @ref{Tracepoint Actions,
collect}.
@kindex info source
@item info source
Show the name of the current source file---that is, the source file for