From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13744 invoked by alias); 21 Feb 2008 00:19:35 -0000 Received: (qmail 13735 invoked by uid 22791); 21 Feb 2008 00:19:35 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Feb 2008 00:19:15 +0000 Received: from zps36.corp.google.com (zps36.corp.google.com [172.25.146.36]) by smtp-out.google.com with ESMTP id m1L0JAEs021380 for ; Wed, 20 Feb 2008 16:19:10 -0800 Received: from rv-out-0910.google.com (rvfc24.prod.google.com [10.140.180.24]) by zps36.corp.google.com with ESMTP id m1L0J98r012571 for ; Wed, 20 Feb 2008 16:19:09 -0800 Received: by rv-out-0910.google.com with SMTP id c24so1844663rvf.16 for ; Wed, 20 Feb 2008 16:19:09 -0800 (PST) Received: by 10.141.178.5 with SMTP id f5mr6204597rvp.112.1203553149374; Wed, 20 Feb 2008 16:19:09 -0800 (PST) Received: by 10.141.142.4 with HTTP; Wed, 20 Feb 2008 16:19:09 -0800 (PST) Message-ID: Date: Thu, 21 Feb 2008 01:06:00 -0000 From: "Doug Evans" To: "Michael Snyder" Subject: Re: gdbserver tracepoint support (from Project Ideas page) Cc: gdb@sourceware.org In-Reply-To: <1203552043.19253.186.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1203552043.19253.186.camel@localhost.localdomain> 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: 2008-02/txt/msg00159.txt.bz2 On Wed, Feb 20, 2008 at 4:00 PM, Michael Snyder wrote: > > Can anyone give me an idea of what they think this involves, and if > > any work has been done on this since the wiki entry was written? > > > What work it involves -- > 1) First gdbserver must understand the extra set of > tracepoint remote protocol commands (or a subset of them: > tracepoint support is very subset-able). I'm sure these > commands are documented somewhere... > 2) Then gdbserver has to know how to implement a tracepoint, > ie. to stop the child, quickly collect a well defined set of > data into a cache, then continue the child without any > interaction with gdb. > > AFAIK no one has worked on it in a while. Thanks. Another question. While there mightn't be much benefit to implementing tracepoints natively as far speed of data collection is concerned, having a consistent u/i and capabilities native vs remote might be reasons to warrant a native implementation. Anyone have any thoughts on a native implementation?