From: Michael Snyder <msnyder@specifix.com>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver tracepoint support (from Project Ideas page)
Date: Thu, 21 Feb 2008 00:19:00 -0000 [thread overview]
Message-ID: <1203552043.19253.186.camel@localhost.localdomain> (raw)
In-Reply-To: <e394668d0802201524s13e4ea08w43a8d1fb9cf9c06b@mail.gmail.com>
On Wed, 2008-02-20 at 15:24 -0800, Doug Evans wrote:
> Hi. The wiki Project Ideas page has this for gdbserver:
>
> * Gdbserver doesn't support tracepoints. A few people have said
> they would work on this, but no patches for it have ever been
> submitted to the mailing list. This could be a nice introductory
> project for someone interested in remote debugging.
>
> Can anyone give me an idea of what they think this involves, and if
> any work has been done on this since the wiki entry was written?
What work it involves --
1) First gdbserver must understand the extra set of
tracepoint remote protocol commands (or a subset of them:
tracepoint support is very subset-able). I'm sure these
commands are documented somewhere...
2) Then gdbserver has to know how to implement a tracepoint,
ie. to stop the child, quickly collect a well defined set of
data into a cache, then continue the child without any
interaction with gdb.
AFAIK no one has worked on it in a while.
next prev parent reply other threads:[~2008-02-21 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 0:01 Doug Evans
2008-02-21 0:19 ` Michael Snyder [this message]
2008-02-21 1:06 ` Doug Evans
2008-02-21 1:34 ` Michael Snyder
2008-02-21 1:36 ` Daniel Jacobowitz
2008-02-21 1:42 ` Doug Evans
2008-02-21 13:44 ` Daniel Jacobowitz
2008-02-21 20:59 ` Michael Snyder
2008-02-22 17:24 ` Doug Evans
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=1203552043.19253.186.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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