From: "André Pönitz" <andre.poenitz@mathematik.tu-chemnitz.de>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: GDB plugin
Date: Tue, 08 May 2012 22:06:00 -0000 [thread overview]
Message-ID: <20120508220615.GB3671@klara.mpi.htwm.de> (raw)
In-Reply-To: <CAOhZP9xmiRwsEUeu5e0FQZXqK3ap-KJEWFDX6izv6rzX-k9a6Q@mail.gmail.com>
On Tue, May 08, 2012 at 11:16:11AM +0530, Abhijit Halder wrote:
> [...] I am not completely aware of the limitation of this approach,
> but it makes me happy thinking that the GDB users who want to extend
> GDB functionality but are not well accustomed with GDB source code,
> can still write their own pluggins and use an enhanced GDB without the
> pain of recompilation of entire GDB source code.
I guess I fit the bill of a "user[s] who want to extend GDB
functionality but are not well accustomed with GDB source code"
rather well. It's something I've been doing for quite a while now.
However, the idea of writing plugins for GDB is not exactly
appealing to me.
For one. the "pain of recompilation of entire GDB source code" you
mention does not exist. It's a straight-forward ./configure &&
make, not even with enough waiting time for a successful trip to
the coffee maker (Unless you are on Windows and need to build all
dependencies, but that would not be different for plugins)
Secondly, GDB is pretty extensible using Python scripting already,
giving "zero compile time" and platform independent access to a lot
of functionality. It's hard to see how compiled plugins would
improve that situation. I'd rather expect the effort for creating
and maintaining a plugin interface to eat into the already scarce
resources of the developers, for really not much benefit.
So, please, pretty please, can we drop the idea? ;-)
Andre'
next prev parent reply other threads:[~2012-05-08 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 16:21 Abhijit Halder
2012-05-07 20:18 ` Tom Tromey
2012-05-08 5:46 ` Abhijit Halder
2012-05-08 14:20 ` Tom Tromey
2012-05-08 15:05 ` Joel Brobecker
2012-05-08 15:21 ` Mark Kettenis
2012-05-08 22:06 ` André Pönitz [this message]
2012-05-09 4:28 ` Abhijit Halder
2012-05-08 6:38 ` Hui Zhu
2012-05-08 13:46 ` Tom Tromey
2012-05-08 14:38 ` Matt Rice
2012-05-08 14:47 ` Paul_Koning
2012-05-08 14:58 ` Matt Rice
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=20120508220615.GB3671@klara.mpi.htwm.de \
--to=andre.poenitz@mathematik.tu-chemnitz.de \
--cc=abhijit.k.halder@gmail.com \
--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