From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "Marc Brünink" <marc@nus.edu.sg>, gdb@sourceware.org
Subject: Re: Tracepoints (and python)
Date: Wed, 02 Jan 2013 17:27:00 -0000 [thread overview]
Message-ID: <87obh75wd1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CANFwon17zRnhfFWG7t9=z8ZY_4AcpsW+6KeXQkM1=H_tG_fr0w@mail.gmail.com> (Hui Zhu's message of "Fri, 21 Dec 2012 16:54:47 +0800")
>>>>> "Hui" == Hui Zhu <teawater@gmail.com> writes:
Hui> I have 3 issues with it:
Hui> 1. Not sure about upstream, but when I use it, it is hard to setup
Hui> tracepoint action with python. How I handle it is write tracepoint
Hui> and action to a GDB source file and call soure command in python
Hui> script.
Yeah, I think you would be better off writing a new Python API to make
tracepoints directly.
Tom
next prev parent reply other threads:[~2013-01-02 17:27 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 [this message]
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
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=87obh75wd1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=marc@nus.edu.sg \
--cc=teawater@gmail.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