From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27221 invoked by alias); 19 Aug 2008 00:33:04 -0000 Received: (qmail 27210 invoked by uid 22791); 19 Aug 2008 00:33:03 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.113.40.141) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 19 Aug 2008 00:32:23 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.64.160]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id E7FA26714; Mon, 18 Aug 2008 17:32:21 -0700 (PDT) Received: from [10.20.92.47] (promb-2s-dhcp47.eng.vmware.com [10.20.92.47]) by mailhost2.vmware.com (Postfix) with ESMTP id CCE8090CB6; Mon, 18 Aug 2008 17:32:21 -0700 (PDT) Message-ID: <48AA1447.9080705@vmware.com> Date: Wed, 20 Aug 2008 16:33:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: "jreiver@free.fr" CC: "gdb@sourceware.org" Subject: Re: Is it possible to use gdb Tracepoint facility with sparc-rtems-gdb? References: <1219097730.48a9f4822ba98@imp.free.fr> In-Reply-To: <1219097730.48a9f4822ba98@imp.free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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-08/txt/msg00226.txt.bz2 Hi, The tracepoint debugging feature depends on support from the remote target side (in this case, tsim-leon3 simulator. The target (simulator) has to be able to interpret certain extra commands and queries from gdb. You would need to ask the suppliers of this simulator whether it knows about these messages. jreiver@free.fr wrote: > Hello, > > I've found in the GDB User Manual a very interesting feature: > "In some applications, it is not feasible for the debugger to interrupt the > program's execution long enough for the developer to learn anything helpful > about its behavior. If the program's correctness depends on its real-time > behavior, delays introduced by a debugger might cause the program to change its > behavior drastically, or perhaps fail, even when the code itself is correct. It > is useful to be able to observe the program's behavior without interrupting it." > > But the GDB user manual also says: > "The tracepoint facility is currently available only for remote targets. See > section Specifying a Debugging Target. 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." > > I'm not sure, but does that mean that the Tracepoint feature is not completely > supported by all targets? > > I have tried to test it by debugging my program with sparc-rtems-gdb, connected > to tsim-leon3 simulator from Gaisler Research: > - I have been able to add tracepoints, enable and disable tracepoints, or make > Tracepoint Action Lists, as specified in GDB user manual > - However, I couldn't start the "Trace experiment" with the "tstart" command, > which returned me this error: > =========================================== > (gdb) tstart > Trace can only be run on remote targets. > =========================================== > > Has anyone ever tried Tracepoint Feature with sparc-rtems-gdb? > Any explanation would be appreciated. > > Thanks. > > JR