From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23407 invoked by alias); 6 Nov 2002 19:12:59 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 23398 invoked from network); 6 Nov 2002 19:12:57 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 6 Nov 2002 19:12:57 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8551E3E60; Wed, 6 Nov 2002 14:12:53 -0500 (EST) Message-ID: <3DC969B5.6030003@redhat.com> Date: Wed, 06 Nov 2002 11:12:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Howell, David P" Cc: Scott Moser , gdb-patches@sources.redhat.com Subject: Re: [PATCH] plugin patch References: <331AD7BED1579543AD146F5A1A44D5251279DE@fmsmsx403.fm.intel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00110.txt.bz2 >> GDB via runtime loaded shared libraries in ways that may not fit with >> the direction of the main GDB tree (not cross-platform, not stable, >> niche audience...). > > For folks like myself that are working on an alternate architecture or > runtime support components (in this case NGPT threads) this would be > very useful, as I can see several info commands that I would like to > add for M:N user mode scheduling state and LWP state display that would > be unique to NGPT and it's implementation. I suspect that if NGPT needs additional thread specific info commands then other thread implementations will be interested in similar. Extending the command set in a generic way also means that a user will find a consistent interface that works across thread implementations. Cf, ``info vector'' which works (well should work) across Altivec, e500 and i386. > Instead of having to add this to the standard gdb as a one-off for NGPT, > I can use the standard gdb and design them as plug-ins to be loaded only > > when debugging NGPT applications. This feels a lot cleaner and could be > applied for other gdb features/architectures to keep the core as small > and efficient as possible, loading additional support/features on demand > only when needed. That is the theory already. Reality differs though, there is always more work to do :-(. That work is, however, independant of a plug-in module. Andrew