Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "jreiver@free.fr" <jreiver@free.fr>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Is it possible to use gdb Tracepoint facility with sparc-rtems-gdb?
Date: Wed, 20 Aug 2008 16:33:00 -0000	[thread overview]
Message-ID: <48AA1447.9080705@vmware.com> (raw)
In-Reply-To: <1219097730.48a9f4822ba98@imp.free.fr>

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


      reply	other threads:[~2008-08-19  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 14:49 jreiver
2008-08-20 16:33 ` Michael Snyder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48AA1447.9080705@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=jreiver@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox