Document -ctf switch of -trace-save

The -trace-save MI command supports saving the trace in the CTF format,
as its CLI counterpart, but it's not documented.

gdb/doc/ChangeLog:

	* gdb.texinfo (GDB/MI Tracepoint Commands): Document -ctf switch
	of -trace-save.
This commit is contained in:
Simon Marchi
2016-10-14 11:39:16 -04:00
parent e913b9cb93
commit 99e61edafe
2 changed files with 10 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2016-10-14 Simon Marchi <simon.marchi@ericsson.com>
* gdb.texinfo (GDB/MI Tracepoint Commands): Document -ctf switch
of -trace-save.
2016-10-06 Tom Tromey <tom@tromey.com>
* guile.texi (Types In Guile): Remove Java mentions.

View File

@ -30934,7 +30934,7 @@ body=[variable=@{name="$trace_timestamp",initial="0"@}
@subsubheading Synopsis
@smallexample
-trace-save [-r ] @var{filename}
-trace-save [ -r ] [ -ctf ] @var{filename}
@end smallexample
Saves the collected trace data to @var{filename}. Without the
@ -30942,6 +30942,10 @@ Saves the collected trace data to @var{filename}. Without the
in a local file. With the @samp{-r} option the target is asked
to perform the save.
By default, this command will save the trace in the tfile format. You can
supply the optional @samp{-ctf} argument to save it the CTF format. See
@ref{Trace Files} for more information about CTF.
@subsubheading @value{GDBN} Command
The corresponding @value{GDBN} command is @samp{tsave}.