From: Daniel Jacobowitz <drow@false.org>
To: "Ryan C. Gordon" <icculus@icculus.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Data plugins for gdb...
Date: Fri, 08 Aug 2008 00:31:00 -0000 [thread overview]
Message-ID: <20080808003020.GA17221@caradoc.them.org> (raw)
In-Reply-To: <489B83F7.2080609@icculus.org>
On Fri, Aug 08, 2008 at 01:23:35AM +0200, Ryan C. Gordon wrote:
>
> I spent a few hours hacking something out as a proof of concept; I'd
> appreciate some opinions from those that know better.
Hi Ryan,
When it rains, it pours - people have complained about GDB's inability
to do this for years, and now it's showing up from all sides.
The GDB project (particularly Vladimir, Tom, and Thiago) is in the
process of adding Python support. One of the intended uses is just
this same idea. They're still designing the command-line interface
to it; I believe Thiago is currently looking into it. Vladimir's also
made it work via MI, so that front-end GUIs can access this
functionality too. There's more information on the PythonGDB wiki
page.
What I don't want is to have a bunch of different extensibility
mechanisms. We've pretty much settled on Python, though of course you
can load C compiled plugins into the Python interpreter; Python just
provides the framework and the boundary.
Can I ask you to work with them? I'm sure there's some of what you
have here that will fit nicely, e.g. the surface plugin, and more
hands are always welcome.
By the way, if you're interested in contributing to GDB (we hope you
are!) you'll probably need a copyright assignment form sooner or
later. Let me know and I can send it to you.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-08 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 23:24 Ryan C. Gordon
2008-08-08 0:31 ` Daniel Jacobowitz [this message]
2008-08-08 4:20 ` Thiago Jung Bauermann
2008-08-08 5:10 ` Ryan C. Gordon
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=20080808003020.GA17221@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=icculus@icculus.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