From: Daniel Jacobowitz <drow@false.org>
To: Neo Jia <neojia@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb plugin status?
Date: Sun, 03 Aug 2008 17:31:00 -0000 [thread overview]
Message-ID: <20080803173108.GA20590@caradoc.them.org> (raw)
In-Reply-To: <5d649bdb0808031010g6330a442xec0415a387d23163@mail.gmail.com>
On Sun, Aug 03, 2008 at 10:10:52AM -0700, Neo Jia wrote:
> hi,
>
> I saw some discussions about the gdb plugin supporting around 2007 but
> it doesn't show up in the project plan page. Now, I am wondering if
> this is on the todo list of the GDB community, or somebody is doing
> this already.
>
> I do expect to have a interface to allow developer to load their own
> plugin in as a module instead using scripts.
We are adding Python support. If you want to write plugins in some
compiled language, you'll be able to load it and access GDB through
a Python middle-layer. It's in progress (see gdb-patches@).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-03 17:31 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 [this message]
2008-08-03 17:43 ` Neo Jia
2008-08-03 21:53 ` Thiago Jung Bauermann
2008-08-03 21:56 ` Thiago Jung Bauermann
[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=20080803173108.GA20590@caradoc.them.org \
--to=drow@false.org \
--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