From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28823 invoked by alias); 21 Feb 2008 00:01:07 -0000 Received: (qmail 28794 invoked by uid 22791); 21 Feb 2008 00:01:04 -0000 X-Spam-Check-By: sourceware.org Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Feb 2008 00:00:45 +0000 Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) by bluesmobile.specifix.com (Postfix) with ESMTP id 6C3893BF54; Wed, 20 Feb 2008 16:00:43 -0800 (PST) Subject: Re: gdbserver tracepoint support (from Project Ideas page) From: Michael Snyder To: Doug Evans Cc: gdb@sourceware.org In-Reply-To: References: Content-Type: text/plain Date: Thu, 21 Feb 2008 00:19:00 -0000 Message-Id: <1203552043.19253.186.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-7.fc7) Content-Transfer-Encoding: 7bit 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/msg00158.txt.bz2 On Wed, 2008-02-20 at 15:24 -0800, Doug Evans wrote: > Hi. The wiki Project Ideas page has this for gdbserver: > > * Gdbserver doesn't support tracepoints. A few people have said > they would work on this, but no patches for it have ever been > submitted to the mailing list. This could be a nice introductory > project for someone interested in remote debugging. > > 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.