Re: [PATCH 4/5] ctf doc and NEWS.

Eli Zaretskii
2013-02-27T18:14:12Z

> From: Yao Qi <yao@codesourcery.com>
> Date: Wed, 27 Feb 2013 10:17:38 +0800
>
> This is almost the same as previous version, except that I update the
> example according to the current output of GDB and write three NEWS
> entries for this series.

Thanks.

> +* The command 'tsave' can now support new option '-ctf' to save trace
> + buffer into Common Trace Format.

"to save the trace buffer in Common Trace Format"

> +--with-babeltrace/--with-babeltrace-include/--with-babeltrace-lib
> + This configure option allows the user to build GDB with
> + libbabeltrace by which GDB can read Common Trace Format data.
^^^^^^^^
"using which"

> + ** The -trace-save MI command can optionally save trace buffer into Common
> + Trace Format now. ^^^^

"in"

> +By default, this command will save trace frame into tfile format.
^^^^
"in"

> @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}

Please have all the @kindex entries before the @item/@itemx lines.

OK with those changes.