From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1047 invoked by alias); 18 Aug 2008 22:15:10 -0000 Received: (qmail 1038 invoked by uid 22791); 18 Aug 2008 22:15:09 -0000 X-Spam-Check-By: sourceware.org Received: from wmproxy1-g27.free.fr (HELO wmproxy1-g27.free.fr) (212.27.42.91) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 18 Aug 2008 22:14:25 +0000 Received: from imp3-g19.priv.proxad.net (imp3-g19.priv.proxad.net [172.20.243.45]) by wmproxy1-g27.free.fr (Postfix) with ESMTP id BB18E2B078 for ; Tue, 19 Aug 2008 00:33:59 +0200 (CEST) Received: by imp3-g19.priv.proxad.net (Postfix, from userid 33) id 5B0AF118CA; Tue, 19 Aug 2008 00:15:30 +0200 (CEST) Received: from ([82.227.65.140]) by imp.free.fr (IMP) with HTTP for ; Tue, 19 Aug 2008 00:15:30 +0200 Message-ID: <1219097730.48a9f4822ba98@imp.free.fr> Date: Wed, 20 Aug 2008 14:49:00 -0000 From: jreiver@free.fr To: gdb@sourceware.org Subject: Is it possible to use gdb Tracepoint facility with sparc-rtems-gdb? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.8 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/msg00225.txt.bz2 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