This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH] More tracepoint doc fixes
- From: Stan Shebs <stan at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Wed, 21 Apr 2010 14:16:36 -0700
- Subject: [PATCH] More tracepoint doc fixes
Self-explanatory, I would imagine. :-)
Stan
2010-04-21 Stan Shebs <stan@codesourcery.com>
* gdb.texinfo (Tracepoint Actions): Mention synonymy of actions
and commands.
(Listing Tracepoints): Update to reflect current behavior.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.708
diff -p -r1.708 gdb.texinfo
*** gdb.texinfo 19 Apr 2010 00:48:44 -0000 1.708
--- gdb.texinfo 21 Apr 2010 20:19:25 -0000
*************** terminate the actions list with a line c
*** 9639,9644 ****
--- 9639,9648 ----
far, the only defined actions are @code{collect}, @code{teval}, and
@code{while-stepping}.
+ @code{actions} is actually equivalent to @code{commands} (@pxref{Break
+ Commands, ,Breakpoint Command Lists}), except that only the defined
+ actions are allowed; any other @value{GDBN} command is rejected.
+
@cindex remove actions from a tracepoint
To remove all actions from a tracepoint, type @samp{actions @var{num}}
and follow it immediately with @samp{end}.
*************** Enter actions for tracepoint 1, one per
*** 9667,9673 ****
> collect bar,baz
> collect $regs
> while-stepping 12
! > collect $fp, $sp
> end
end
@end smallexample
--- 9671,9677 ----
> collect bar,baz
> collect $regs
> while-stepping 12
! > collect $pc, arr[i]
> end
end
@end smallexample
*************** collect all local variables.
*** 9692,9698 ****
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.
--- 9696,9702 ----
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.
*************** tracing:
*** 9763,9786 ****
@itemize @bullet
@item
its passcount as given by the @code{passcount @var{n}} command
- @item
- its step count as given by the @code{while-stepping @var{n}} command
- @item
- its action list as given by the @code{actions} command. The actions
- are prefixed with an @samp{A} so as to distinguish them from commands.
@end itemize
@smallexample
(@value{GDBP}) @b{info trace}
Num Type Disp Enb Address What
1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7
pass count 1200
- step count 20
- A while-stepping 20
- A collect globfoo, $regs
- A end
- A collect globfoo2
- A end
(@value{GDBP})
@end smallexample
--- 9767,9784 ----
@itemize @bullet
@item
its passcount as given by the @code{passcount @var{n}} command
@end itemize
@smallexample
(@value{GDBP}) @b{info trace}
Num Type Disp Enb Address What
1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7
+ while-stepping 20
+ collect globfoo, $regs
+ end
+ collect globfoo2
+ end
pass count 1200
(@value{GDBP})
@end smallexample