Re: [PATCH] Add CTF support to GDB [4/4] doc

[Hui Zhu <teawater@gmail.com>]

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

On Fri, Nov 23, 2012 at 3:39 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 23 Nov 2012 10:27:36 +0800
>> From: Hui Zhu <hui_zhu@mentor.com>
>> CC: <gdb-patches@sourceware.org>
>>
>> Following part is for NEWS:
>> * GDB now has the ability to read and write trace buffer in common trace
>>    format (CTF).  To create a CTF trace file, use "tsave -ctf <filename>",
>>    and to use it, do "target ctf <name>".
>                     ^^
> "use"
>
>> +By default, this command will save trace frame into tfile format.
>> +You can supply the optional argument @code{-ctf} to save date in CTF
>> +format.  The Common Trace Format (CTF) is proposed as a trace format
>
> Use @dfn when you first introduce new terminology:
>
>   The @dfn{Common Trace Format} (CTF) is proposed as a trace format ...
>
>> +that suits the needs of the embedded, telecom, high-performance
>> +and kernel communities.  Please goto @url{http://www.efficios.com/ctf}
>> +get more information about it.       ^^^^
>
> You want @indicateurl, not @url here.
>
> OK with these changes.

NEWS:
* GDB now has the ability to read and write trace buffer in common trace
  format (CTF).  To create a CTF trace file, use "tsave -ctf <filename>",
  and use it, do "target ctf <name>".

And post a new version according to your mail.

Thanks,
Hui

2012-11-27  Hui Zhu  <hui_zhu@mentor.com>

	* gdb.texinfo (Trace Files): Add "tsave -ctf" and target ctf.

[-- Attachment #2: ctf-doc.txt --]
[-- Type: text/plain, Size: 1479 bytes --]

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -12069,7 +12069,7 @@ of trace data, via the @code{target tfil
 @table @code
 
 @kindex tsave
-@item tsave [ -r ] @var{filename}
+@item tsave [ -r ] [-ctf] @var{filename}
 Save the trace data to @var{filename}.  By default, this command
 assumes that @var{filename} refers to the host filesystem, so if
 necessary @value{GDBN} will copy raw trace data up from the target and
@@ -12078,6 +12078,12 @@ optional argument @code{-r} (``remote'')
 the data directly into @var{filename} in its own filesystem, which may be
 more efficient if the trace buffer is very large.  (Note, however, that
 @code{target tfile} can only read from files accessible to the host.)
+By default, this command will save trace frame into tfile format.
+You can supply the optional argument @code{-ctf} to save date in CTF
+format.  The @dfn{Common Trace Format} (CTF) is proposed as a trace format
+that suits the needs of the embedded, telecom, high-performance
+and kernel communities.  Please goto @indicateurl{http://www.efficios.com/ctf}
+get more information about it.
 
 @kindex target tfile
 @kindex tfile
@@ -12089,6 +12095,11 @@ the state of the trace run at the moment
 as the current trace frame you are examining.  @var{filename} must be
 on a filesystem accessible to the host.
 
+@kindex target ctf
+@kindex ctf
+@item target ctf @var{filename}
+Use the file named @var{filename} as a source of CTF trace data.
+
 @end table
 
 @node Overlays