From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5853 invoked by alias); 26 Jan 2006 13:41:29 -0000 Received: (qmail 5845 invoked by uid 22791); 26 Jan 2006 13:41:28 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 26 Jan 2006 13:41:27 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1F27NN-0000oz-4V for gdb@sourceware.org; Thu, 26 Jan 2006 08:41:25 -0500 Date: Thu, 26 Jan 2006 13:41:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: Using XML in GDB? Message-ID: <20060126134124.GA3107@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <20060126055744.GA29647@nevyn.them.org> <43D8BB89.4090900@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D8BB89.4090900@st.com> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00262.txt.bz2 On Thu, Jan 26, 2006 at 12:07:37PM +0000, Andrew STUBBS wrote: > I don't have anything to add to the XML debate yet. The idea of the > "target available feature" interface sounds interesting and may be of > use to us here, but I am having a little difficulty tracking down > details. I have found the beginning of this conversation in the May > archives, but it is always harder to find the definitive conclusion. > > Is there anywhere you can point me to find the final specification of > what this interface will include - what features will it describe, what > aspects of those features are covered? Is it just limited to registers? There isn't a definitive conclusion because it's evolved substantially once I began (re-) implementing it. This is what I had two weeks ago: http://sourceware.org/ml/gdb/2005-05/msg00171.html But it doesn't look entirely like that any more. Registers can be generically described without hard-coded GDB knowledge. Most other features can't, except for their presence or absence. But the point of suggesting XML is to keep this extensible should someone have a bright idea :-) -- Daniel Jacobowitz CodeSourcery