aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorStan Shebs <shebs@codesourcery.com>2009-12-31 17:47:43 +0000
committerStan Shebs <shebs@codesourcery.com>2009-12-31 17:47:43 +0000
commit6da95a677b977e132bc936a73b2bb92844b14f32 (patch)
tree85f0857e05cc28c9838bda2cf7129bccfb465657 /gdb/doc
parent383e5f855398acb5ff53f32cde88bdfa675d7931 (diff)
downloadgdb-6da95a677b977e132bc936a73b2bb92844b14f32.zip
gdb-6da95a677b977e132bc936a73b2bb92844b14f32.tar.gz
gdb-6da95a677b977e132bc936a73b2bb92844b14f32.tar.bz2
Add new tracepoint action teval.
* tracepoint.c (teval_pseudocommand): New function. (validate_actionline): Add teval action case. (encode_actions): Ditto. (_initialize_tracepoint): Define teval pseudocommand. * NEWS: Mention teval. * gdb.texinfo (Tracepoint Actions): Describe teval. * gdb.trace/actions.exp: Test teval action.
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/gdb.texinfo9
2 files changed, 13 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 7171423..6c5bfe7 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2009-12-31 Stan Shebs <stan@codesourcery.com>
+
+ * gdb.texinfo (Tracepoint Actions): Describe teval.
+
2009-12-29 Stan Shebs <stan@codesourcery.com>
* gdb.texinfo (Tracepoint Actions): Describe default-collect.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 39f0d67..f7bc686 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -9626,6 +9626,15 @@ 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 teval @r{(tracepoints)}
+@item teval @var{expr1}, @var{expr2}, @dots{}
+Evaluate the given expressions when the tracepoint is hit. This
+command accepts a comma-separated list of expressions. The results
+are discarded, so this is mainly useful for assigning values to trace
+state variables (@pxref{Trace State Variables}) without adding those
+values to the trace buffer, as would be the case if the @code{collect}
+action were used.
+
@kindex while-stepping @r{(tracepoints)}
@item while-stepping @var{n}
Perform @var{n} single-step traces after the tracepoint, collecting