From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31424 invoked by alias); 20 Apr 2007 19:57:11 -0000 Received: (qmail 31413 invoked by uid 22791); 20 Apr 2007 19:57:10 -0000 X-Spam-Check-By: sourceware.org Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Apr 2007 20:57:07 +0100 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.50) id 1HezE8-00017E-QO; Fri, 20 Apr 2007 19:57:04 +0000 Message-ID: <46291B10.F439FB8B@dessent.net> Date: Fri, 20 Apr 2007 19:57:00 -0000 From: Brian Dessent Reply-To: gdb@sourceware.org X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: Thiago Jung Bauermann CC: gdb ml Subject: Re: plugin interface for GDB References: <1177098228.20179.10.camel@localhost.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00126.txt.bz2 Thiago Jung Bauermann wrote: > Scott Moser's idea was to have very basic plugin support (loading and > unloading), and leave to the plugin writer the work of searching which > internal GDB functions he'd need to use and directly call them from the > plugin code. I am more inclined to go into a different direction, which > is to provide an abstraction layer which would expose functionality > which is potentially useful for a plugin. You should read the recent threads about adding scripting support to gdb. The one from several months ago seemed to mostly converge on Python, with tcl and guile as runners up. To me it seems like it would be a lot easier to go in that direction than to actually allow for plugins in the sense of dynamically loading a shared module of compiled code. In either case, you have to implement some kind of API that exposes the internals of gdb to the plugin or the script, and in either case you can extend the functionality of gdb in pretty much arbitrary ways. But in the case of scripting you don't have ABI headaches to worry about, and it increases accessilbility since you can express relatively high level concepts easily in just a short amount of python script, compared to having to code the same amount of functionality with a C plugin. Brian