From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9147 invoked by alias); 12 Jun 2012 23:36:26 -0000 Received: (qmail 9029 invoked by uid 22791); 12 Jun 2012 23:36:25 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-junco.atl.sa.earthlink.net (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Jun 2012 23:36:13 +0000 Received: from [68.96.200.16] (helo=macbook2.local) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1SeadA-0006uX-EL for gdb@sourceware.org; Tue, 12 Jun 2012 19:36:12 -0400 Message-ID: <4FD7D268.9090105@earthlink.net> Date: Tue, 12 Jun 2012 23:36:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Re: What about add new commands "maintenance agent-breakpoint id expression" and "maintenance agent-eval-breakpoint id expression" References: <4FD68A1A.2040600@mentor.com> In-Reply-To: <4FD68A1A.2040600@mentor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da94093a90ff8b73984c59284cbbefac03baf350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00060.txt.bz2 On 6/11/12 5:15 PM, Hui Zhu wrote: > Hi guys, > > The "maintenance agent" and "maintenance agent-eval" are for translate > an expression into remote agent bytecode. > Both of them got address info from frame. But when we use tracepoint > or breakpoint with agent code, this address is from tracepoint or > breakpoint. > > What about add new commands "maintenance agent-breakpoint id > expression" and "maintenance agent-eval-breakpoint id expression"? > Then we can get the agent code for breakpoint or tracepoint directly. I could see something like that being useful - instead of breakpoint id I would suggest having it take a linespec, so you don't have to create a tracepoint just to see what the bytecodes would be. Also, an optional hyphen-argument like "-at " would save defining new maintenance subcommands. One caveat though - not all collect actions translate into agent expressions, so the user could be misled into thinking that the target was running bytecode instead of doing direct collection. (This distinction confused me at least once a while back - the bug was in non-agent collect action.) Stan stan@codesourcery.com