From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14362 invoked by alias); 18 Apr 2014 13:11:23 -0000 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 Received: (qmail 14351 invoked by uid 89); 18 Apr 2014 13:11:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 18 Apr 2014 13:11:21 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1Wb8ZZ-0005m8-FQ from Vladimir_Prus@mentor.com ; Fri, 18 Apr 2014 06:11:17 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 18 Apr 2014 06:11:16 -0700 Received: from [172.30.88.157] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.2.247.3; Fri, 18 Apr 2014 14:11:15 +0100 Message-ID: <53512470.8080305@codesourcery.com> Date: Fri, 18 Apr 2014 16:30:00 -0000 From: Vladimir Prus User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Bob Rossi CC: Andrew Burgess , Subject: Re: MI async status output References: <20140409210803.GA3166@linux> <5346B226.40209@cs.msu.su> <20140410201259.GA15060@linux> <5347BD84.5030200@broadcom.com> <20140412002538.GA27657@linux> <5350E049.9070705@codesourcery.com> <20140418104619.GA26892@linux> In-Reply-To: <20140418104619.GA26892@linux> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2014-04/txt/msg00060.txt.bz2 On 18.04.2014 14:46, Bob Rossi wrote: >> whereas MI has grammar, the fact that actual output does not always match the >> grammar is well known. This specific problem was not known to me. >> >> It is obviously possible to fix in a parser. It's also possible to fix in GDB, >> but as usual the question of what existing frontends might depend on this behaviour. > > Thanks for the response. I'm writing a new grammar that will be open > source that handles as many possible outputs that GDB outputs, for as > many possible GDB versions. I'm writing unit and system tests to > validate this effort. Is this a part of some larger effort? > I'm taking notes every time i have to modify the parser to detail the > reasons why. > > When I'm done, perhaps we can update GDB's manual with the new grammar > that I constuct, considering the one in the manual is just plain wrong. That would be helpful; ideally we'd clearly mark, in the grammar, the cases where actual GDB behaviour differs from desirable behaviour, so that these can be eliminated if anybody starts MI3. Though quite possibly, MI3 should just accept and produce JSON. -- Vladimir Prus CodeSourcery / Mentor Graphics http://www.mentor.com/embedded-software/