From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Neo Jia <neojia@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb plugin status?
Date: Sun, 03 Aug 2008 21:56:00 -0000 [thread overview]
Message-ID: <1217800536.29321.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1217800323.29321.3.camel@localhost.localdomain>
(Sorry, sent message too early.)
On Sun, 2008-08-03 at 18:52 -0300, Thiago Jung Bauermann wrote:
> On Sun, 2008-08-03 at 10:42 -0700, Neo Jia wrote:
> > I am wondering if this is feasible. My plugin will be implemented in C
> > as it needs to access the hardware. And I should be able to use it
> > from gdb through the Python middle-layer as Python provides the way to
> > access .so file.
> >
> > Am I right?
>
> Yes, it should work.
By the way, if there's any functionality or usecase that you have in
mind which is not described or not covered in
http://sourceware.org/gdb/wiki/PythonGdb
please let us know. We are very interested in input from potential users
of the Python support.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2008-08-03 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 17:11 Neo Jia
2008-08-03 17:31 ` Daniel Jacobowitz
2008-08-03 17:43 ` Neo Jia
2008-08-03 21:53 ` Thiago Jung Bauermann
2008-08-03 21:56 ` Thiago Jung Bauermann [this message]
[not found] ` <5d649bdb0808040042o34b759edxe6c11e16588214f6@mail.gmail.com>
2008-08-04 14:28 ` Thiago Jung Bauermann
2008-08-05 7:33 ` Neo Jia
2008-08-05 13:47 ` Thiago Jung Bauermann
[not found] ` <5d649bdb0808051553g6ee22cbfr80cfa43cd56e870c@mail.gmail.com>
2008-08-06 3:27 ` Thiago Jung Bauermann
2008-08-06 4:40 ` Tom Tromey
2008-08-06 5:44 ` Thiago Jung Bauermann
2008-08-06 20:37 ` Tom Tromey
2008-08-06 20:46 ` Thiago Jung Bauermann
2008-08-07 7:11 ` Neo Jia
2008-08-07 18:37 ` Tom Tromey
2008-08-07 19:06 ` Thiago Jung Bauermann
2008-08-12 15:25 ` Thiago Jung Bauermann
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=1217800536.29321.7.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=neojia@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