From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32281 invoked by alias); 27 Feb 2013 02:18:43 -0000 Received: (qmail 32204 invoked by uid 22791); 27 Feb 2013 02:18:41 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,FROM_12LTRDOM,KHOP_RCVD_UNTRUST,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; Wed, 27 Feb 2013 02:18:35 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1UAWbL-0001po-34 from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Tue, 26 Feb 2013 18:18:35 -0800 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 26 Feb 2013 18:18:35 -0800 Received: from qiyao.dyndns.org.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.1.289.1; Tue, 26 Feb 2013 18:18:34 -0800 From: Yao Qi To: Subject: [PATCH 0/5, 2nd try] CTF Support Date: Wed, 27 Feb 2013 02:18:00 -0000 Message-ID: <1361931459-3953-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain 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: 2013-02/txt/msg00669.txt.bz2 Hi, This patch series is to teach GDB to save trace buffer into Common Trace Format (CTF) and also read CTF file. Hui posted the V1 some months ago and got some comments in the review. In order to get these patches accepted by FSF GDB, we redesign the patches and here is the V2. At present, GDB is using TFILE format to save trace buffers and trace saving logic is coupled with this format to some extent. In order to save trace buffer in CTF, we did two things, 1) Decouple trace saving code with any specific trace file format (such as TFILE). This is what patch 1/5 does. 2) Use CTF in a way similar to TFILE, which will reduce the cost of supporting CTF. Usually TFILE trace file is composed by two parts, definition part and trace buffer data part. The latter is composed by multiple trace frames, which is composed by different types of blocks. In CTF, we have similar concepts "packet" and "event". A packet is composed by several events, which can be of different types. We can use "packet" to represent trace frame and "event" to represent block. The definition part is human readable, about trace status, tracepoint definitions, etc. They can be easily mapped to a certain type of CTF event. In this version, we haven't saved trace status, tracepoint definitions, and trace variable definitions into CTF trace file. This doesn't prevent user using this feature, and we'll address them in the follow up patch series. -- 1.7.7.6