From: Simon Marchi Date: Fri, 14 Oct 2016 15:39:17 +0000 (-0400) Subject: Fix typos in trace commands doc X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=be06ba8ceb2197b6771f8e47dc7b8df316e1da75;p=binutils-gdb.git Fix typos in trace commands doc gdb/doc/ChangeLog: * gdb.texinfo (Using Trace Files): Fix typo. (GDB/MI Tracepoint Commands): Likewise. --- diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 9517627d2f9..4f4ce5c049e 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2016-10-14 Simon Marchi + + * gdb.texinfo (Using Trace Files): Fix typo. + (GDB/MI Tracepoint Commands): Likewise. + 2016-10-14 Simon Marchi * gdb.texinfo (GDB/MI Tracepoint Commands): Document -ctf switch diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index d4196261475..b3eb4885cf5 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -13678,7 +13678,7 @@ 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 in tfile format. -You can supply the optional argument @code{-ctf} to save date in CTF +You can supply the optional argument @code{-ctf} to save data in CTF format. The @dfn{Common Trace Format} (CTF) is proposed as a trace format that can be shared by multiple debugging and tracing tools. Please go to @indicateurl{http://www.efficios.com/ctf} to get more information. @@ -30960,7 +30960,7 @@ The corresponding @value{GDBN} command is @samp{tsave}. -trace-start @end smallexample -Starts a tracing experiments. The result of this command does not +Starts a tracing experiment. The result of this command does not have any fields. @subsubheading @value{GDBN} Command