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.