Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hui_zhu@mentor.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add CTF support to GDB [4/4] doc
Date: Wed, 28 Nov 2012 01:40:00 -0000	[thread overview]
Message-ID: <CANFwon2E3vG8hMwaVz_+u0spLHPw_qth+BSOWzOVHdi5e3i2_g@mail.gmail.com> (raw)
In-Reply-To: <83vccqx6hf.fsf@gnu.org>

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

  reply	other threads:[~2012-11-28  1:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  1:46 Hui Zhu
2012-11-21 17:37 ` Eli Zaretskii
2012-11-23  2:28   ` Hui Zhu
2012-11-23  7:40     ` Eli Zaretskii
2012-11-27 11:17       ` Hui Zhu
2012-11-27 18:11         ` Eli Zaretskii
2012-11-28  1:40           ` Hui Zhu [this message]
2012-11-28  2:44             ` Yao Qi
2012-11-28  4:56               ` Hui Zhu
     [not found]                 ` <50B5A064.2010007@codesourcery.com>
2012-11-28  5:52                   ` Hui Zhu
2012-11-28 17:40                     ` Eli Zaretskii
2013-01-14 12:26                       ` Hui Zhu
2013-01-14 16:05                         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANFwon2E3vG8hMwaVz_+u0spLHPw_qth+BSOWzOVHdi5e3i2_g@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox