From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15188 invoked by alias); 7 Dec 2004 19:50:34 -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 15017 invoked from network); 7 Dec 2004 19:50:20 -0000 Received: from unknown (HELO lakermmtao09.cox.net) (68.230.240.30) by sourceware.org with SMTP; 7 Dec 2004 19:50:20 -0000 Received: from white ([68.9.64.121]) by lakermmtao09.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041207195020.UYAC7152.lakermmtao09.cox.net@white>; Tue, 7 Dec 2004 14:50:20 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1CblLn-0003Hf-00; Tue, 07 Dec 2004 14:50:19 -0500 Date: Tue, 07 Dec 2004 19:50:00 -0000 From: Bob Rossi To: Eli Zaretskii Cc: kostik@ispras.ru, gdb@sources.redhat.com Subject: Re: complete GDB MI specification Message-ID: <20041207195019.GB12487@white> Mail-Followup-To: Eli Zaretskii , kostik@ispras.ru, gdb@sources.redhat.com References: <3616850089.20041129165854@ispras.ru> <41AB43C8.7050500@gnu.org> <13730878711.20041129205245@ispras.ru> <18220744048.20041206192130@ispras.ru> <01c4dbd6$Blat.v2.2.2$0b225460@zahav.net.il> <429477215.20041207214436@ispras.ru> <20041207185849.GA12487@white> <01c4dc95$Blat.v2.2.2$63201020@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4dc95$Blat.v2.2.2$63201020@zahav.net.il> User-Agent: Mutt/1.3.28i X-SW-Source: 2004-12/txt/msg00046.txt.bz2 On Tue, Dec 07, 2004 at 09:45:01PM +0200, Eli Zaretskii wrote: > > Date: Tue, 7 Dec 2004 13:58:49 -0500 > > From: Bob Rossi > > Cc: Eli Zaretskii , gdb@sources.redhat.com > > > > Well, if you plan on doing this, as I do, it would be helpful if there > > were some place's in GDB's doco that we could contribute back information > > that we think is helpful. > > Sorry, I don't understand: what is ``back information'' that you are > talking about? Why not simply add the documentation to the manual? hehe, very sorry. Just bad English. What I meant to say was, It would be helpful if there was a place in the GDB manual that had all of the MI commands for specific versions of MI, and all of the fields that the MI command is capable of outputting. Basically, the semantic information needed to write a parser and quickly interpret the MI commands as correct or incorrect output, and what each field means. Thanks, Bob Rossi