From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6076 invoked by alias); 12 Apr 2011 22:33:23 -0000 Received: (qmail 6064 invoked by uid 22791); 12 Apr 2011 22:33:21 -0000 X-SWARE-Spam-Status: No, hits=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Tue, 12 Apr 2011 22:33:15 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p3CMX7rN022473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Apr 2011 18:33:07 -0400 Received: from psique (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p3CMX5lH003725; Tue, 12 Apr 2011 18:33:05 -0400 From: Sergio Durigan Junior To: Pedro Alves Cc: gdb-patches@sourceware.org, Tom Tromey Subject: Re: [PATCH 3/6] Modify internalvar mechanism References: <201104121224.31901.pedro@codesourcery.com> Date: Tue, 12 Apr 2011 22:33:00 -0000 In-Reply-To: <201104121224.31901.pedro@codesourcery.com> (Pedro Alves's message of "Tue, 12 Apr 2011 12:24:31 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2011-04/txt/msg00177.txt.bz2 Pedro Alves writes: > On Monday 04 April 2011 04:08:34, Sergio Durigan Junior wrote: >> Hi, >> >> This patch modifies the mechanism of internalvar. It basically adds >> more manipulation functions to them (`compile_to_ax' and `destroy'), and >> updates the definitions and pointers of existing internalvars. > > Can you explain this? Why would you want to compile an internal var > to AX, for example? A SystemTap probe can have up to 10 arguments. In our original plan, the idea is that the user should be able to collect those arguments using the tracepoint mechanism. Since we already have the necessary code to evaluate an argument (which is treated as an internal varibale inside GDB), we thought it would be easier to extend this code in order to compile it to AX. You could do something like: (gdb) trace probe:test .. (gdb) actions .. > collect $_probe_arg0 > end .. In order to collect the probe's first argument, and so on. > It would be imensely helpful if patches came with a high > level explanation of why they are necessary in the first > place. :-/ My fault, sorry. Regards, Sergio.