From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12292 invoked by alias); 29 Nov 2012 20:47:04 -0000 Received: (qmail 12212 invoked by uid 22791); 29 Nov 2012 20:47:00 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Nov 2012 20:46:53 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qATKkouH002824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Nov 2012 15:46:50 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id qATKkmT4011143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 29 Nov 2012 15:46:49 -0500 From: Tom Tromey To: Hui Zhu Cc: Subject: Re: [PATCH] Add CTF support to GDB [3/4] ctf target References: <50AC323F.1070907@mentor.com> Date: Thu, 29 Nov 2012 20:47:00 -0000 In-Reply-To: <50AC323F.1070907@mentor.com> (Hui Zhu's message of "Wed, 21 Nov 2012 09:45:35 +0800") Message-ID: <87pq2w3znr.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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/msg00898.txt.bz2 >>>>> "Hui" == Hui Zhu writes: Hui> It add a new target ctf like the tfile target to read the ctf file. Hui> After use this target open the ctf dir, you can use tfind to select Hui> the ctf event. Each field inside this event will add to GDB as a Hui> internalvar. And tdump will show all of them. And you can use python Hui> read the value of them. Can you explain the internalvar feature a little? Why is it needed? How are these variables named? What do they represent? Are they different from the saved trace data somehow? I notice this feature isn't in the documentation at all -- I think that is required, perhaps with an example. Tom