From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27264 invoked by alias); 4 Feb 2004 03:31:04 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 27257 invoked from network); 4 Feb 2004 03:31:03 -0000 Received: from unknown (HELO demos.bsdclusters.com) (69.55.225.36) by sources.redhat.com with SMTP; 4 Feb 2004 03:31:03 -0000 Received: from demos.bsdclusters.com (demos [69.55.225.36]) by demos.bsdclusters.com (8.12.8p1/8.12.8) with ESMTP id i143V008039577; Tue, 3 Feb 2004 19:31:00 -0800 (PST) (envelope-from kmacy@fsmware.com) Received: from localhost (kmacy@localhost) by demos.bsdclusters.com (8.12.8p1/8.12.8/Submit) with ESMTP id i143Uxfh039558; Tue, 3 Feb 2004 19:30:59 -0800 (PST) X-Authentication-Warning: demos.bsdclusters.com: kmacy owned process doing -bs Date: Wed, 04 Feb 2004 03:31:00 -0000 From: Kip Macy X-X-Sender: kmacy@demos.bsdclusters.com To: Kevin Buettner cc: gdb@sources.redhat.com Subject: Re: gdb + perl In-Reply-To: <20040203140551.53a2052c@saguaro> Message-ID: <20040203192253.D36518@demos.bsdclusters.com> References: <20040130153706.N34716@demos.bsdclusters.com> <20040130193848.B41210@demos.bsdclusters.com> <20040203140551.53a2052c@saguaro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-02/txt/msg00014.txt.bz2 > 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