[PATCH v2] tracepoint: add new trace command "printf" and agent expression "printf" [3] doc

Hui Zhu
2011-02-24T08:54:28Z

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]

This patch is for doc.

Thanks,
Hui

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

* agentexpr.texi (Bytecode Descriptions): Add printf.
* gdb.texinfo (Tracepoint Action Lists): Add printf.

[-- Attachment #2: tp_print_doc.txt --]
[-- Type: text/plain, Size: 1481 bytes --]

---
doc/agentexpr.texi | 7 +++++++
doc/gdb.texinfo | 6 ++++++
2 files changed, 13 insertions(+)

--- a/doc/agentexpr.texi
+++ b/doc/agentexpr.texi
@@ -489,6 +489,13 @@ named @code{trace_quick16}, for consiste
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
--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -10242,6 +10242,12 @@ state variables (@pxref{Trace State Vari
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,