From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: "Vincent Bénony" <bsr.dfk@gmail.com>
Cc: Daniel Jacobowitz <drow@false.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB C plugin system, and STL container viewer as an example
Date: Tue, 27 May 2008 18:21:00 -0000 [thread overview]
Message-ID: <1211738585.7957.125.camel@localhost.localdomain> (raw)
In-Reply-To: <834CF078-7D51-4A8C-A23D-3113485DCBC8@nordnet.fr>
On Sun, 2008-05-25 at 14:36 +0200, Vincent Bénony wrote:
> Sure, I'll have a look at your API as soon as possible, and try to
> write a cleaner version of my.... euh... stuff ;-)
That would be awesome.
> do you have some
> kind of doc ? (sorry if you've already answered to this)
Not yet, sorry. Python support is in the early days yet. I think this
patch from Vladimir is a bit in the direction of your work, so maybe it
will help you to have a look at it:
http://sourceware.org/ml/gdb-patches/2008-05/msg00106.html
Also, the "Python support in GDB" patch series is all we currently have
in terms of Python support. That code was taken from the git repo. You
can find information about how to access it here:
http://sourceware.org/gdb/wiki/OngoingWork
Feel free to ask about Python integration stuff on the GDB mailing list,
or on the #gdb channel at freenode.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-05-25 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 18:34 Vincent Benony
2008-05-23 19:30 ` Vladimir Prus
2008-05-23 19:53 ` Daniel Jacobowitz
2008-05-27 18:17 ` Vincent Bénony
2008-05-27 18:21 ` Thiago Jung Bauermann [this message]
2008-05-23 19:59 ` Vincent Benony
2008-05-23 20:31 ` Vladimir Prus
2008-05-23 20:39 ` Vincent Benony
2008-05-23 20:46 ` Vladimir Prus
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=1211738585.7957.125.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=bsr.dfk@gmail.com \
--cc=drow@false.org \
--cc=gdb-patches@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