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

[Hui Zhu <hui_zhu@mentor.com>]

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

This is the doc patch for the ctf read and write function.

Thanks,
Hui

2012-11-20  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: 1234 bytes --]

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -12086,7 +12086,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
@@ -12095,6 +12095,9 @@ 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.
 
 @kindex target tfile
 @kindex tfile
@@ -12106,6 +12109,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