2009-12-28 Stan Shebs <stan@codesourcery.com>

[deliverable/binutils-gdb.git] / gdb / NEWS

diff --git a/gdb/NEWS b/gdb/NEWS
index 8c0fd92b9fff5c597f49b35cac4852a7a5b918c7..b680d9be6b73c02fd09981a355f0a55592ee40cc 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -24,6 +24,19 @@ Renesas RX                   rx
   lists inferiors that are not running yet or that have exited
   already.  See also "New commands" and "New options" below.
 
+* Trace state variables
+
+  GDB tracepoints now include support for trace state variables, which
+  are variables managed by the target agent during a tracing
+  experiment.  They are useful for tracepoints that trigger each
+  other, so for instance one tracepoint can count hits in a variable,
+  and then a second tracepoint has a condition that is true when the
+  count reaches a particular value.  Trace state variables share the
+  $-syntax of GDB convenience variables, and can appear in both
+  tracepoint actions and condition expressions.  Use the "tvariable"
+  command to create, and "info tvariables" to view; see "Trace State
+  Variables" in the manual for more detail.
+  
 * Changed commands
 
 disassemble
@@ -75,6 +88,15 @@ set remotebreak [on | off]
 show remotebreak
 Deprecated.  Use "set/show remote interrupt-sequence" instead.
 
+tvariable $NAME [ = EXP ]
+  Create or modify a trace state variable.
+
+info tvariables
+  List trace state variables and their values.
+
+delete tvariable $NAME ...
+  Delete one or more trace state variables.
+
 * New options
 
 set follow-exec-mode new|same
@@ -83,6 +105,14 @@ show follow-exec-mode
   creates a new one.  This is useful to be able to restart the old
   executable after the inferior having done an exec call.
 
+* New remote packets
+
+QTDV
+   Define a trace state variable.
+
+qTV
+   Get the current value of a trace state variable.
+
 * Bug fixes
 
 Process record now works correctly with hardware watchpoints.