Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nicholas Mc Guire <hofrat@opentech.at>
To: Michael Snyder <msnyder@vmware.com>
Cc: sumanth <sumanth.gundapneni@redpinesignals.com>,
		gdb <gdb@sourceware.org>
Subject: Re: TRACE implementation
Date: Wed, 21 Oct 2009 14:52:00 -0000	[thread overview]
Message-ID: <20091021143535.GA32672@opentech.at> (raw)
In-Reply-To: <4ADF17B1.6030100@vmware.com>

On Wed, 21 Oct 2009, Michael Snyder wrote:

> sumanth wrote:
>> Hi ,
>>
>>        I am talking about "gdb tracepoints" only. I am asking for "How  
>> can I implement them in GDB ?"
>
> Great.  Thanks for the clarification.
> Partial answer: you don't have to implement them in gdb.
> They're already implemented in gdb.
>
>>        means, where I can start with. Heard something about remote 
>> stubs 
>
> Yes, that's correct.  GDB already knows how to tell a stub
> to collect trace data.  You need to implement a stub that
> understands the trace commands that gdb will send to it.

One implementation for GDB 6.3-6.6 is available at

ftp://dslab.lzu.edu.cn/pub/gdb_tracepoints

this is the stubs in gdbserver and a few (bug)fixes in the core
gdb routines that were needed.

thx!
hofrat


  reply	other threads:[~2009-10-21 14:35 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 [this message]
2009-10-23 15:54       ` sumanth
2009-10-23 16:48         ` Michael Snyder
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=20091021143535.GA32672@opentech.at \
    --to=hofrat@opentech.at \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --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