Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: sumanth <sumanth.gundapneni@redpinesignals.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: TRACE implementation
Date: Fri, 23 Oct 2009 16:48:00 -0000	[thread overview]
Message-ID: <4AE1D016.3070200@vmware.com> (raw)
In-Reply-To: <4AE132F6.9010800@redpinesignals.com>

sumanth wrote:
> Hi Michael,
>                     Very pleased with the information you provided. 
> Still I have certain doubts in mind.
>                     Tracepoints can b implemented through either remote 
> stubs or gdbserver or gdb agents (byte-coding).
>                      Is this 
> true?..................................................
>                      which can be best suited to me as I am accessing my 
> fpga/processor through a parallel port jtag. I dont want to
>                     burden my processor by running a server on it.
>                     The problem here , I googled in net and I didn't 
> even find a single prototype to have a fell of how to trace data(trace 
> points)  on my target .

Sumanth,

How does gdb talk to your jtag device?  Is it
a) directly to the parallel port, or
b) through a serial connection to an agent that controls the parallel port?

If b, and if using the gdb remote serial protocol, then there's your
agent into which you can add the tracepoint smarts.

Michael


  reply	other threads:[~2009-10-23 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  9:06 sumanth
2009-10-20 19:33 ` Michael Snyder
2009-10-21  5:41   ` sumanth
2009-10-21 14:26     ` Michael Snyder
2009-10-21 14:52       ` Nicholas Mc Guire
2009-10-23 15:54       ` sumanth
2009-10-23 16:48         ` Michael Snyder [this message]
2009-10-24 14:13           ` sumanth
     [not found] <F7CE05678329534C957159168FA70DEC5157AEBFC9@EUSAACMS0703.eamcs.ericsson.se>
2009-10-21 14:22 ` Dominique Toupin

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=4AE1D016.3070200@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=sumanth.gundapneni@redpinesignals.com \
    /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