From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18480 invoked by alias); 19 Mar 2008 11:20:01 -0000 Received: (qmail 18471 invoked by uid 22791); 19 Mar 2008 11:20:00 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Mar 2008 11:19:43 +0000 Received: (qmail 11546 invoked from network); 19 Mar 2008 11:19:41 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 19 Mar 2008 11:19:41 -0000 From: Vladimir Prus To: Bob Rossi Subject: Re: MI non-stop mode spec Date: Wed, 19 Mar 2008 12:01:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: gdb@sources.redhat.com References: <200803190016.02072.vladimir@codesourcery.com> <20080319110938.GF12641@brasko.net> In-Reply-To: <20080319110938.GF12641@brasko.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803191419.39958.vladimir@codesourcery.com> 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 X-SW-Source: 2008-03/txt/msg00155.txt.bz2 On Wednesday 19 March 2008 14:09:38 Bob Rossi wrote: > On Wed, Mar 19, 2008 at 12:16:01AM +0300, Vladimir Prus wrote: > > > > Making good used of GDB in async mode, and especially in async non-stop > > mode demands some changes in MI -- both general clarifications, and actual > > work to allow most MI commands while the target is running and define > > their behaviour. > > Do you mind posting an updated grammar for the GDB/MI changes that you > are making? or at least just a diff of it? The following changes will happen: output ==> ( out-of-band-record )* [ result-record ] "(gdb)" nl becomes: output ==> ( out-of-band-record | result-record | "(gdb)" ) nl then async-class ==> "stopped" | others (where others will be added depending on the needs--this is still in development). becomes: async-class ==> "stopped" | "running" | "thread-created" | others (where others will be added depending on the needs--this is still in development). > I currently maintain a gdb/mi bison parser that i have not put into > production use yet. However, the time for this is coming, I will > probably start working on this again after all of these changes get > through. Except for the 'output' change -- which essentially codifies that MI output is a sequence of almost independent lines, I don't think there are further changes to the grammar planned except for adding new async-classes. > At one point, I would parse all of the output of gdb/mi that came > from running 'make check' in the gdb.mi testsuite. If you would like, > I could do that again after your patch, and let you know where it > breaks. That would be good, thanks. - Volodya