From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: GDB plugin
Date: Tue, 08 May 2012 05:46:00 -0000 [thread overview]
Message-ID: <CAOhZP9xmiRwsEUeu5e0FQZXqK3ap-KJEWFDX6izv6rzX-k9a6Q@mail.gmail.com> (raw)
In-Reply-To: <87vck7wxs7.fsf@fleche.redhat.com>
On Tue, May 8, 2012 at 1:48 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Abhijit" == Abhijit Halder <abhijit.k.halder@gmail.com> writes:
>
> Abhijit> Is there any way to load a GDB plugin (shared library having extended
> Abhijit> functionality) in current GDB? I am planning to develop one. Need
> Abhijit> yours opinion on this.
>
> There is a little bit of this for the JIT functionality.
>
> Generic plugins are trouble because they tend to fix the API -- but we
> want to be able to change the API as needed. The JIT approach avoided
> this by exporting a custom, minimal API.
>
> What exactly are you planning to do?
>
I am planning to introduce a pluggin command in GDB which will give a
flexibility to a GDB user to develop his/her own GDB extension (e.g.
GDB-ext.so). The extension may have new and/or extended functionality
like support for new languages and platforms and custom GDB-command.
The extension can be loaded by this newly proposed plugin command.
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.
Thanks,
Abhijit Halder
> Tom
next prev parent reply other threads:[~2012-05-08 5:46 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 [this message]
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
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=CAOhZP9xmiRwsEUeu5e0FQZXqK3ap-KJEWFDX6izv6rzX-k9a6Q@mail.gmail.com \
--to=abhijit.k.halder@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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