From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7140 invoked by alias); 27 Jul 2004 02:31: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 7047 invoked from network); 27 Jul 2004 02:31:44 -0000 Received: from unknown (HELO neptune.TidalNetworks.net) (67.114.153.34) by sourceware.org with SMTP; 27 Jul 2004 02:31:44 -0000 Content-class: urn:content-classes:message Subject: "Debugging stubs for supporting tracepoint" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Jul 2004 03:37:00 -0000 Message-ID: <52BBA75459915749B68F93B604B636CD21AC@neptune.TidalNetworks.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "xinan tang" To: X-SW-Source: 2004-07/txt/msg00339.txt.bz2 Hi Hi=20 The following is except from doc., "Debugging with GDB": ____________________________________________________________=20 The tracepoint facility is currently available only for remote targets.=20 See Chapter 16[Targets], page 143. In addition, your remote target=20 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? Thanks --Xinan