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

On Fri, 30 Jan 2004 19:42:30 -0800 (PST)
Kip Macy <kmacy@fsmware.com> wrote:

> I know it is bad form to follow-up on one's own messages, but since I
> took the time to pull the changes into 6.0 I thought I'd make them
> available to anyone who might be curious about it.
> 
> Documentation:
> http://www.fsmware.com/gdb/gdb_ffi.html
> Tarball:
> http://www.fsmware.com/gdb/gdb-6.0-perl.tgz
> 
> perl support can be turned on by passing --enable-ffiperl to configure.
> 
> Even if it isn't deemed appropriate for mainline inclusion, I'm eager to
> hear any feedback.

Thanks for making your changes available.

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

My hunch is that you'll have a hard time getting these changes into
mainline GDB.  The reason for this hunch is as follows:

  1) I don't think that perl would be the first choice for an
     extension language for very many of the GDB maintainers.  That
     said, if we were to take a vote, I have no idea what the first
     choice would be.

  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 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 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.

Kevin


  reply	other threads:[~2004-02-03 21:06 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 [this message]
2004-02-04  3:31     ` Kip Macy
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=20040203140551.53a2052c@saguaro \
    --to=kevinb@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kmacy@fsmware.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