From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15272 invoked by alias); 19 Mar 2008 11:10:15 -0000 Received: (qmail 15264 invoked by uid 22791); 19 Mar 2008 11:10:15 -0000 X-Spam-Check-By: sourceware.org Received: from vms042pub.verizon.net (HELO vms042pub.verizon.net) (206.46.252.42) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Mar 2008 11:09:55 +0000 Received: from black ([71.245.67.80]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JXZ00IMT5O38KV2@vms042.mailsrvcs.net> for gdb@sources.redhat.com; Wed, 19 Mar 2008 06:09:40 -0500 (CDT) Received: from bob by black with local (Exim 4.67) (envelope-from ) id 1JbwAt-0003MB-3C; Wed, 19 Mar 2008 07:09:39 -0400 Date: Wed, 19 Mar 2008 11:16:00 -0000 From: Bob Rossi Subject: Re: MI non-stop mode spec In-reply-to: <200803190016.02072.vladimir@codesourcery.com> To: Vladimir Prus Cc: gdb@sources.redhat.com Mail-followup-to: Vladimir Prus , gdb@sources.redhat.com Message-id: <20080319110938.GF12641@brasko.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <200803190016.02072.vladimir@codesourcery.com> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-IsSubscribed: yes 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/msg00153.txt.bz2 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? 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. 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. Thanks, Bob Rossi