From: sumanth <sumanth.gundapneni@redpinesignals.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: TRACE implementation
Date: Wed, 21 Oct 2009 05:41:00 -0000 [thread overview]
Message-ID: <4ADE9702.20300@redpinesignals.com> (raw)
In-Reply-To: <4ADDF8D4.4010100@vmware.com>
Hi ,
I am talking about "gdb tracepoints" only. I am asking for "How
can I implement them in GDB ?"
means, where I can start with. Heard something about remote stubs
.....
Michael , Can you be a bit more brief on "published API" which
you mentioned in your last response.
Thanks,
Sumanth G
Michael Snyder wrote:
> sumanth wrote:
>> Hi,
>> I am trying to implement trace in my port. Can anyone point me
>> where in
>> gdb source I can refer to? Any helpful documents.
>
> What do you mean by "trace"?
>
> Have you looked at gdb tracepoints? Is this close to what
> you are looking for? See the url:
> http://sourceware.org/gdb/current/onlinedocs/gdb_14.html#SEC95
>
>
>>
>> Once my trace is implemented , I have data in trace buffer.
>> How can I convert the data
>> from trace buffer and display it to user. Heard there are 3rd
>> party tools which comes in handy .
>
> If you are talking about tracepoints (see above), and if
> you can make your trace buffer talk to gdb according to the
> published API, you can use gdb to display your trace results.
>
> If not, you need to tell us more about what you're trying to do.
>
>
>> If any , please mail me. (preferably some gdb gui).
>>
>> PS: I am novice in gdb implementation .
>>
>> Thanks,
>> Sumanth G
>>
>
>
>
next prev parent reply other threads:[~2009-10-21 5:16 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 [this message]
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
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=4ADE9702.20300@redpinesignals.com \
--to=sumanth.gundapneni@redpinesignals.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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