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

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

[Hui Zhu]

[-- 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

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

[Eli Zaretskii]

> Date: Wed, 21 Nov 2012 09:45:49 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> 
> This is the doc patch for the ctf read and write function.

Thanks.

> +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.

We need to add here one or two sentences explaining what "CTF" stands
for and perhaps giving a URL where the reader can learn more about
that.

The fact that we support CTF should also be in NEWS.

Otherwise, OK.

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

[Hui Zhu]

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

On 11/22/12 01:36, Eli Zaretskii wrote:
>> Date: Wed, 21 Nov 2012 09:45:49 +0800
>> From: Hui Zhu <hui_zhu@mentor.com>
>>
>> This is the doc patch for the ctf read and write function.
>
> Thanks.
>
>> +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.
>
> We need to add here one or two sentences explaining what "CTF" stands
> for and perhaps giving a URL where the reader can learn more about
> that.
>
> The fact that we support CTF should also be in NEWS.
>
> Otherwise, OK.
>

Post a new version according to your comments.

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>".

Thanks,
Hui

[-- Attachment #2: ctf-doc.txt --]
[-- Type: text/plain, Size: 1465 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 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.
 
 @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

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

[Eli Zaretskii]

> 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.

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

[Hui Zhu]

[-- 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

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

[Eli Zaretskii]

> From: Hui Zhu <teawater@gmail.com>
> Date: Tue, 27 Nov 2012 19:17:09 +0800
> Cc: Hui Zhu <hui_zhu@mentor.com>, gdb-patches@sourceware.org
> 
> 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 to use it, type "target ctf <name>".

> +and kernel communities.  Please goto @indicateurl{http://www.efficios.com/ctf}
> +get more information about it.

"to get more information"

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

[Hui Zhu]

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

On Wed, Nov 28, 2012 at 2:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Tue, 27 Nov 2012 19:17:09 +0800
>> Cc: Hui Zhu <hui_zhu@mentor.com>, gdb-patches@sourceware.org
>>
>> 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 to use it, type "target ctf <name>".
>
>> +and kernel communities.  Please goto @indicateurl{http://www.efficios.com/ctf}
>> +get more information about it.
>
> "to get more information"

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, type "target ctf <name>".

Post a new version according to your comments.

Thanks,
Hui

2012-11-28  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: 1473 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}
+to get more information.
 
 @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

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

[Yao Qi]

On 11/28/2012 09:40 AM, Hui Zhu wrote:
> --- 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}

According patch 1/4 (function ctf_save), 'tsave -ctf foo' will save ctf 
files into directory 'foo'.  If so, we have to reflect this in document.

Can we do 'tsave -r -ctf foo'?  IIRC, it is not allowed.

It can be written something like this,

   @item tsave [ -r ] @var{filename}
   @itemx tsave [-ctf] @var{dirname}

> @@ -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.
> +

According to patch 3/4 (function init_ctf_ops), 'target ctf foo' uses 
directory foo instead of file foo.

-- 
Yao (齐尧)

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

[Hui Zhu]

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

On 11/28/12 10:44, Yao Qi wrote:
> On 11/28/2012 09:40 AM, Hui Zhu wrote:
>> --- 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}
>
> According patch 1/4 (function ctf_save), 'tsave -ctf foo' will save ctf files into directory 'foo'.  If so, we have to reflect this in document.
>
> Can we do 'tsave -r -ctf foo'?  IIRC, it is not allowed.
>
> It can be written something like this,
>
>    @item tsave [ -r ] @var{filename}
>    @itemx tsave [-ctf] @var{dirname}
>
>> @@ -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.
>> +
>
> According to patch 3/4 (function init_ctf_ops), 'target ctf foo' uses directory foo instead of file foo.
>

Post a new version according to your comments.

Thanks,
Hui

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

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -12070,6 +12070,7 @@ of trace data, via the @code{target tfil
 
 @kindex tsave
 @item tsave [ -r ] @var{filename}
+@itemx tsave [-ctf] @var{dirname}
 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 +12079,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}
+to get more information.
 
 @kindex target tfile
 @kindex tfile
@@ -12089,6 +12096,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{dirname}
+Use the directory named @var{dirname} as a source of CTF trace data.
+
 @end table
 
 @node Overlays

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

[Hui Zhu]

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

On Wed, Nov 28, 2012 at 1:25 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 11/28/2012 12:56 PM, Hui Zhu wrote:
>>
>> +By default, this command will save trace frame into tfile format.
>> +You can supply the optional argument @code{-ctf} to save date in CTF
>
>                                                             ^^^^ typo.
>
>> @@ -12089,6 +12096,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{dirname}
>> +Use the directory named @var{dirname} as a source of CTF trace data.
>> +
>>   @end table
>
>
> I am not good at documentation, but I feel that it might be better to
> combine the doc for 'target tfile' and 'target ctf' together, because they
> (should) behave almost the same to users, how about this?
>
> @kindex target tfile
> @kindex tfile
> @item target tfile @var{filename}
> @kindex target ctf
> @kindex ctf
> @itemx target ctf @var{dirname}
> Use the file named @var{filename} or directory named @var{dirname} as a
> source of trace data.  Commands
> that examine data work as they do with a live target, but it is not
> possible to run any new trace experiments.  @code{tstatus} will report
> the state of the trace run at the moment the data was saved, as well
> as the current trace frame you are examining.  @var{filename} or
> @var{dirname} must be
>
> on a filesystem accessible to the host.
>
> I have no other comments.
>
> --
> Yao (齐尧)

I think that is better.  Post a new version according to your comments.

Thanks,
Hui

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, type "target ctf <name>".

2012-11-28  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: 2065 bytes --]

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -12070,6 +12070,7 @@ of trace data, via the @code{target tfil
 
 @kindex tsave
 @item tsave [ -r ] @var{filename}
+@itemx tsave [-ctf] @var{dirname}
 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,16 +12079,26 @@ 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}
+to get more information.
 
 @kindex target tfile
 @kindex tfile
 @item target tfile @var{filename}
-Use the file named @var{filename} as a source of trace data.  Commands
-that examine data work as they do with a live target, but it is not
-possible to run any new trace experiments.  @code{tstatus} will report
-the state of the trace run at the moment the data was saved, as well
-as the current trace frame you are examining.  @var{filename} must be
-on a filesystem accessible to the host.
+@kindex target ctf
+@kindex ctf
+@itemx target ctf @var{dirname}
+Use the file named @var{filename} or directory named @var{dirname} as
+a source of trace data.  Commands that examine data work as they do with
+a live target, but it is not possible to run any new trace experiments.
+@code{tstatus} will report the state of the trace run at the moment
+the data was saved, as well as the current trace frame you are examining.
+@var{filename} or @var{dirname} must be on a filesystem accessible to
+the host.
 
 @end table
 

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

[Eli Zaretskii]

> From: Hui Zhu <teawater@gmail.com>
> Date: Wed, 28 Nov 2012 13:51:15 +0800
> Cc: Hui Zhu <hui_zhu@mentor.com>, Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
> 
> I think that is better.  Post a new version according to your comments.
> 
> Thanks,
> Hui
> 
> 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, type "target ctf <name>".
> 
> 2012-11-28  Hui Zhu  <hui_zhu@mentor.com>
> 
> 	* gdb.texinfo (Trace Files): Add "tsave -ctf" and target ctf.

This is OK, thanks.

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

[Hui Zhu]

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

Hi Eli,

To make the "target ctf" more clear.  I add a small example for it in the doc.
Please help me review it.

Thanks,
Hui

2013-01-14  Hui Zhu  <hui_zhu@mentor.com>

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

On Thu, Nov 29, 2012 at 1:39 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Wed, 28 Nov 2012 13:51:15 +0800
>> Cc: Hui Zhu <hui_zhu@mentor.com>, Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>>
>> I think that is better.  Post a new version according to your comments.
>>
>> Thanks,
>> Hui
>>
>> 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, type "target ctf <name>".
>>
>> 2012-11-28  Hui Zhu  <hui_zhu@mentor.com>
>>
>>       * gdb.texinfo (Trace Files): Add "tsave -ctf" and target ctf.
>
> This is OK, thanks.

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

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -12069,6 +12069,7 @@ of trace data, via the @code{target tfil
 
 @kindex tsave
 @item tsave [ -r ] @var{filename}
+@itemx tsave [-ctf] @var{dirname}
 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
@@ -12077,16 +12078,45 @@ 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}
+to get more information.
 
 @kindex target tfile
 @kindex tfile
 @item target tfile @var{filename}
-Use the file named @var{filename} as a source of trace data.  Commands
-that examine data work as they do with a live target, but it is not
-possible to run any new trace experiments.  @code{tstatus} will report
-the state of the trace run at the moment the data was saved, as well
-as the current trace frame you are examining.  @var{filename} must be
-on a filesystem accessible to the host.
+@kindex target ctf
+@kindex ctf
+@itemx target ctf @var{dirname}
+Use the file named @var{filename} or directory named @var{dirname} as
+a source of trace data.  Commands that examine data work as they do with
+a live target, but it is not possible to run any new trace experiments.
+@code{tstatus} will report the state of the trace run at the moment
+the data was saved, as well as the current trace frame you are examining.
+@var{filename} or @var{dirname} must be on a filesystem accessible to
+the host.
+
+@smallexample
+(@value{GDBP}) target ctf ctf.ctf
+(@value{GDBP}) tfind
+warning: $d is not support.
+warning: $c is not support.
+warning: $d is not support.
+warning: $c is not support.
+Found trace frame 0, tracepoint 2
+../../../gdb/gdb/testsuite/gdb.trace/ctf.c:24
+(@value{GDBP}) tdump
+$d = void
+$c = void
+$b = 1
+$a = 0
+$i = 0
+(@value{GDBP}) p $b
+$1 = 1
+@end smallexample
 
 @end table
 

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

[Eli Zaretskii]

> From: Hui Zhu <teawater@gmail.com>
> Date: Mon, 14 Jan 2013 20:25:07 +0800
> Cc: yao@codesourcery.com, hui_zhu@mentor.com, gdb-patches@sourceware.org
> 
> To make the "target ctf" more clear.  I add a small example for it in the doc.
> Please help me review it.

Thanks, this is fine with me.