Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb + perl
Date: Wed, 04 Feb 2004 03:31:00 -0000	[thread overview]
Message-ID: <20040203192253.D36518@demos.bsdclusters.com> (raw)
In-Reply-To: <20040203140551.53a2052c@saguaro>


> Thanks for making your changes available.

Thanks for replying.

>
> I happen to like the idea of providing access to perl from GDB, but then
> I also happen to like perl.

I happen to really *not like* perl. However, this is targeted at the
developers at my company who predominantly do like perl.  I don't know
what would be the ideal language. I've actually started ocaml support.
As far as mainstream scripting languages go, I would've chosen python.
I've structured the such that the only real work is writing a parser
for MI output in the target language. I export the MI functionality and
callback mechanism through a language independent interface.


>   2) GDB is a GNU project and as such would probably use guile as its
>      primary extension language.  (Of course, there could be others.)

I would add support for guile if doing so would get the FFI code
incorporated into mainline GDB.


>
> I haven't looked at your work at all yet.  Do you think it would be
> possible to develop an extension language API that could be used by
> perl as well as other extension languages?

That wouldn't be a giant leap.

> That way, it'd be possible
> to do extension language plugins, of which your work would be one.
> It'd also be possible (and easier) to maintain the code you've written
> independent of mainline GDB.

On a more general note I'd like to see loadable module support added to
GDB. This would allow people to maintain GDB extensions independently of
GDB. There are a number of things that I see adding to GDB that are only
interesting if you have a very large complex system and hence would
never be interesting for the majority of GDB users.


			-Kip


  reply	other threads:[~2004-02-04  3:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  0:05 Kip Macy
2004-01-31  3:42 ` Kip Macy
2004-02-03 21:06   ` Kevin Buettner
2004-02-04  3:31     ` Kip Macy [this message]
2004-02-04  4:13       ` Daniel Jacobowitz
2004-02-04  5:44         ` Kip Macy
2004-02-04  6:01           ` Eli Zaretskii
2004-02-04 17:00 ` Andrew Cagney
2004-02-04 17:36   ` Kip Macy
2004-02-04 17:48   ` Bob Rossi

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=20040203192253.D36518@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@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