+2011-02-24 Joel Brobecker <brobecker@adacore.com>
+
+ Revert the following patch (code patch was not approved):
+ 2011-02-21 Hui Zhu <teawater@gmail.com>
+ * agentexpr.texi (bytecode descriptions): add printf.
+ * gdb.texinfo (tracepoint action lists): add printf.
+
2011-02-23 Doug Evans <dje@google.com>
* gdb.texinfo (Symbols In Python): Fix mention of C++, use C@t{++}.
Record the value of trace state variable number @var{n} in the trace
buffer. The handling of @var{n} is as described for @code{getv}.
-@item @code{printf} (0x31) @var{n} @var{template}: @result{}
-Print the values in the stack under the control of the string template.
-The end of @var{template} is 0x00.
-If @var{n} is 0, just output the string template.
-If @var{n} is 1, pop a value from the stack and print it under the control
-of the string template.
-
@item @code{end} (0x27): @result{}
Stop executing bytecode; the result should be the top element of the
stack. If the purpose of the expression was to compute an lvalue or a
values to the trace buffer, as would be the case if the @code{collect}
action were used.
-@kindex printf
-@item printf @var{template}, @var{expressions}@dots{}
-Print the values of one or more @var{expressions} under the control of
-the string @var{template} in @code{gdbserver} part.
-The command format is with simple @code{printf} (@pxref{Output, printf}).
-
@kindex while-stepping @r{(tracepoints)}
@item while-stepping @var{n}
Perform @var{n} single-step instruction traces after the tracepoint,