From: "Marc Brünink" <marc@nus.edu.sg>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb <gdb@sourceware.org>
Subject: Re: Tracepoints (and python)
Date: Fri, 11 Jan 2013 07:29:00 -0000 [thread overview]
Message-ID: <728CB725-036A-4285-8FCE-3A1D6705926D@nus.edu.sg> (raw)
In-Reply-To: <CADPb22Ss8KfBBxnVg4fgjEH_m_+XOsFRjiNY2V6HPK5n3BG3fw@mail.gmail.com>
On Jan 3, 2013, at 1:44 AM, Doug Evans wrote:
> On Wed, Jan 2, 2013 at 10:28 AM, Tom Tromey <tromey@redhat.com> wrote:
>> Marc> 1. Is there any technical reason why tracing is only possible on
>> Marc> remote targets? Or is is "just" not implemented for anything else.
>>
>> Tom> I think the only reason is that nobody has done it.
>>
>> Doug> This is part of gdb/gdbserver feature parity desires right?
>>
>> It is on the list on the wiki, but I think just to mention it as a
>> difference. We (meaning Red Hat) plan to tackle most of the items on
>> that list, but I don't think this is one we are going to do.
>
> [Sorry for the resend, previous one got sent as text/html.]
>
> Thanks.
>
> For clarity's sake for Marc,
> what's needed isn't so much an implementation as a (pretty
> significant) refactor.
Interesting. Actually I am trying to implement a rudimentary application tracer using the python interface. So far I have simply used breakpoints. It works like a charm but is obviously very slow. Thus, I want to switch to tracepoints. Having access to tracepoints during native debugging would be nice but is not necessary. This is a point for my personal wish list.
Another issue is the trace buffer. It would be nice to get a notification as soon as the trace buffer is full. Currently gdbserver does not sent one (assuming gdb is connected), does it?
Marc
next prev parent reply other threads:[~2013-01-11 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 2:36 Marc Brünink
2012-12-20 14:33 ` Tom Tromey
2012-12-21 8:55 ` Hui Zhu
2013-01-02 17:27 ` Tom Tromey
2012-12-28 0:43 ` Doug Evans
2013-01-02 17:28 ` Tom Tromey
2013-01-02 17:44 ` Doug Evans
2013-01-11 7:29 ` Marc Brünink [this message]
2013-01-11 8:12 ` Yao Qi
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=728CB725-036A-4285-8FCE-3A1D6705926D@nus.edu.sg \
--to=marc@nus.edu.sg \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).