From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29665 invoked by alias); 23 Nov 2012 02:28:13 -0000 Received: (qmail 29657 invoked by uid 22791); 23 Nov 2012 02:28:12 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Nov 2012 02:27:41 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1TbizU-0004qo-8O from Hui_Zhu@mentor.com ; Thu, 22 Nov 2012 18:27:40 -0800 Received: from SVR-ORW-FEM-03.mgc.mentorg.com ([147.34.97.39]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Nov 2012 18:27:39 -0800 Received: from [127.0.0.1] (147.34.91.1) by svr-orw-fem-03.mgc.mentorg.com (147.34.97.39) with Microsoft SMTP Server id 14.1.289.1; Thu, 22 Nov 2012 18:27:39 -0800 Message-ID: <50AEDF18.6090707@mentor.com> Date: Fri, 23 Nov 2012 02:28:00 -0000 From: Hui Zhu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Eli Zaretskii CC: Subject: Re: [PATCH] Add CTF support to GDB [4/4] doc References: <50AC324D.7010703@mentor.com> <83r4nmvowo.fsf@gnu.org> In-Reply-To: <83r4nmvowo.fsf@gnu.org> Content-Type: multipart/mixed; boundary="------------090500070708010201000309" X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00605.txt.bz2 --------------090500070708010201000309 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Content-length: 862 On 11/22/12 01:36, Eli Zaretskii wrote: >> Date: Wed, 21 Nov 2012 09:45:49 +0800 >> From: Hui Zhu >> >> This is the doc patch for the ctf read and write function. > > Thanks. > >> +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. > > We need to add here one or two sentences explaining what "CTF" stands > for and perhaps giving a URL where the reader can learn more about > that. > > The fact that we support CTF should also be in NEWS. > > Otherwise, OK. > Post a new version according to your comments. Following part is for 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 ", and to use it, do "target ctf ". Thanks, Hui --------------090500070708010201000309 Content-Type: text/plain; charset="us-ascii"; name="ctf-doc.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ctf-doc.txt" Content-length: 1465 --- 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 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 @url{http://www.efficios.com/ctf} +get more information about it. @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 --------------090500070708010201000309--