From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: Michael Snyder <msnyder@specifix.com>, gdb@sourceware.org
Subject: Re: gdbserver tracepoint support (from Project Ideas page)
Date: Thu, 21 Feb 2008 13:44:00 -0000 [thread overview]
Message-ID: <20080221014238.GB26767@caradoc.them.org> (raw)
In-Reply-To: <e394668d0802201735q53b3a971w8a55f0c876ba1300@mail.gmail.com>
On Wed, Feb 20, 2008 at 05:35:58PM -0800, Doug Evans wrote:
> hasn't been implemented. A hybrid approach would be way cool (i.e.
> instrumenting the target program so tracepoints didn't stop the
> program even when running natively - this is where remote targets have
> an advantage, the stub is already in the same address space and
> process - but that ups the complexity a wee bit).
Hmm, uprobes + SystemTap...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-21 1:43 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
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 [this message]
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=20080221014238.GB26767@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.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