2011-02-21 Hui Zhu <teawater@gmail.com>

* agentexpr.texi (Bytecode Descriptions): Add printf.
	* gdb.texinfo (Tracepoint Action Lists): Add printf.
This commit is contained in:
Hui Zhu 2011-02-21 08:40:27 +00:00
parent f9c6ff7236
commit f994e27a0b
3 changed files with 18 additions and 0 deletions

@ -1,3 +1,8 @@
2011-02-21 Hui Zhu <teawater@gmail.com>
* agentexpr.texi (Bytecode Descriptions): Add printf.
* gdb.texinfo (Tracepoint Action Lists): Add printf.
2011-02-18 Tom Tromey <tromey@redhat.com>
* agentexpr.texi (Bytecode Descriptions): Document pick and rot.

@ -489,6 +489,13 @@ named @code{trace_quick16}, for consistency.
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

@ -10242,6 +10242,12 @@ 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 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,