From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4161 invoked by alias); 12 Mar 2005 17:13:21 -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 4076 invoked from network); 12 Mar 2005 17:13:16 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 12 Mar 2005 17:13:16 -0000 Received: from zaretski (tony03-42-6.inter.net.il [80.230.42.6]) by legolas.inter.net.il (MOS 3.5.6-GR) with ESMTP id DXO07548 (AUTH halo1); Sat, 12 Mar 2005 19:12:41 +0200 (IST) Date: Sat, 12 Mar 2005 17:13:00 -0000 From: "Eli Zaretskii" To: Bob Rossi Message-ID: <01c52726$Blat.v2.4$82600ae0@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: bpisupat@cs.indiana.edu, gdb@sources.redhat.com In-reply-to: <20050312144054.GA18379@white> (message from Bob Rossi on Sat, 12 Mar 2005 09:40:54 -0500) Subject: Re: MI starting guide Reply-to: Eli Zaretskii References: <20050312000437.GA17327@white> <01c526ee$Blat.v2.4$37bafb40@zahav.net.il> <20050312144054.GA18379@white> X-SW-Source: 2005-03/txt/msg00140.txt.bz2 > Date: Sat, 12 Mar 2005 09:40:54 -0500 > From: Bob Rossi > Cc: bpisupat@cs.indiana.edu, gdb@sources.redhat.com > > Honestly Eli, there are so many improvements that we could add, the sky > is the limit. In fact, I have several ideas of improving the MI > interface doco, of course, none of this will get done if the patch review > time issue isn't resolved. There's no need to wait for the patch review issue to get resolved. Since I'm the area maintainer for the documentation, I can approve doco patches myself. And I usually review such patches the moment I read them. > - obviously a section on 'asycnronous' MI interface, which I still > don't understand the purpose of (since I can't get any of the > asynchronous commands to work) > - make sure that the documented "example" commands section stay up > to date with what GDB actually outputs. I have a funny feeling that > many of the commands do not actually output the same info anymore. > (we could generate the example data from a testsuite case, and diff > what GDB currently outputs to what it is supposed to output to > make sure the data doesn't change) > - Document what MI commands are implemented/unimplemented > - Document the correct MI output command grammar (which is almost > correct, but not really) > - Somehow document what versions each command was introduced in > - A developers howto guide (Although, I think the reference > implementation I was talking about would be a better way to > describe this) > - Document what MI fields are mandatory output for a command, and > which ones are optional. These are all good ideas, so feel free. I suggest to pick up some aspect of MI that you know best, or that doesn't require a too deep knowledge of the implementation (e.g., the implemented/unimplemented thing), and start with that.