From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11828 invoked by alias); 6 Apr 2010 20:13:07 -0000 Received: (qmail 11486 invoked by uid 22791); 6 Apr 2010 20:12:52 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Apr 2010 20:12:47 +0000 Received: (qmail 3617 invoked from network); 6 Apr 2010 20:12:45 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 6 Apr 2010 20:12:45 -0000 Message-ID: <4BBB95B7.4070106@codesourcery.com> Date: Tue, 06 Apr 2010 20:13:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Doug Evans CC: Pedro Alves , gdb-patches@sourceware.org Subject: Re: gdbserver tracepoints support proper References: <201004050021.39083.pedro@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-04/txt/msg00109.txt.bz2 Doug Evans wrote: > On Sun, Apr 4, 2010 at 4:21 PM, Pedro Alves wrote: > >> This finally adds a trace agent to gdbserver, and enough glue >> to make it work for x86-linux. >> > > For reference sake, > there's no technical reason why gdb itself can't support tracepoints, right? > [IWBN to use tracepoints on linux, for example, without having to use gdbserver] > > I suppose not - you could try defining native versions of the tracepoint methods, convert tracepoint insertion to breakpoint insertion, manage the trace buffer within GDB, have agent expression evaluation call target vector to get registers or memory. You'd have to do some trickiness with bpstats, and maybe extend target vector, so that if GDB sees a tracepoint hit via remote protocol, it's a bad error, but if native, it's handled more like a breakpoint with a command list. Stan