From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5832 invoked by alias); 27 Jul 2004 03:37:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5821 invoked from network); 27 Jul 2004 03:37:43 -0000 Received: from unknown (HELO calvin.codito.co.in) (203.199.140.162) by sourceware.org with SMTP; 27 Jul 2004 03:37:43 -0000 Received: from [192.168.100.52] (arnor.codito.co.in [192.168.100.52]) by calvin.codito.co.in (8.12.10/8.12.10) with ESMTP id i6R3YZFn006809; Tue, 27 Jul 2004 09:04:36 +0530 Subject: Re: "Debugging stubs for supporting tracepoint" From: Ramana Radhakrishnan Reply-To: ramana.radhakrishnan@codito.com To: xinan tang Cc: gdb@sources.redhat.com In-Reply-To: <52BBA75459915749B68F93B604B636CD21AC@neptune.TidalNetworks.net> References: <52BBA75459915749B68F93B604B636CD21AC@neptune.TidalNetworks.net> Content-Type: text/plain Organization: Codito Technologies Date: Tue, 27 Jul 2004 04:07:00 -0000 Message-Id: <1090899435.15802.8.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00340.txt.bz2 Hi, > Hi > > > > Hi > > The following is except from doc., "Debugging with GDB": > > ____________________________________________________________ > The tracepoint facility is currently available only for remote targets. > See Chapter 16[Targets], page 143. In addition, your remote target > must know how to collect trace data. This functionality is implemented > in the remote stub; however, none of the stubs distributed > with gdb support tracepoints as of this writing. > This chapter describes the tracepoint commands and features. > ------------------------------------------------------------------ > > Then question is where to get start if one wants to implement > tracepoint support on remote stubs? In the remote stub, you would need the stub to collect data per tracepoint whenever it is hit. Right , so what are tracepoints ? Tracepoints can be thought of to be equivalent to software breakpoints from an implementation point of view and the commands / actions need to be executed at the time the tracepoint is hit . So in your stub you would determine whether a breakpoint or a tracepoint has been hit when the inferior stops and then store the data needed in whatever format needed. (Commands / Actions which have been specified for the tracepoints about which you can find info in the Agent Expression chapter in the manual / ax-gdb.c in the source tree.) . The mailing list archives could give you some idea regarding the same also. AFAIK none of the existing stubs in the source tree support them. cheers ramana