From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2175 invoked by alias); 8 Dec 2004 18:30:10 -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 1907 invoked from network); 8 Dec 2004 18:29:44 -0000 Received: from unknown (HELO lakermmtao05.cox.net) (68.230.240.34) by sourceware.org with SMTP; 8 Dec 2004 18:29:44 -0000 Received: from white ([68.9.64.121]) by lakermmtao05.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041208182944.VSPS28432.lakermmtao05.cox.net@white>; Wed, 8 Dec 2004 13:29:44 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1Cc6ZK-0003jC-00; Wed, 08 Dec 2004 13:29:42 -0500 Date: Wed, 08 Dec 2004 18:30:00 -0000 From: Bob Rossi To: Konstantin Karganov Cc: gdb@sources.redhat.com Subject: Re: complete GDB MI specification Message-ID: <20041208182942.GA14313@white> Mail-Followup-To: Konstantin Karganov , 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> <01c4dc95$Blat.v2.2.2$0f2f1c40@zahav.net.il> <9825395456.20041208194459@ispras.ru> <20041208165327.GA13964@white> <13729177144.20041208204801@ispras.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13729177144.20041208204801@ispras.ru> User-Agent: Mutt/1.3.28i X-SW-Source: 2004-12/txt/msg00058.txt.bz2 On Wed, Dec 08, 2004 at 08:48:01PM +0300, Konstantin Karganov wrote: > Hello Bob, > > > I just will not have time for a few months. > > If you want to work on such a project, I could start you out with what I > > have so far. > It seems that I'll have to develop my own parser and refine the MI > response semantics to build a debugger over it. > Currently planning to use Boost Spirit parser generator. > > > the simplest solution would be to provide a second yacc parser > And then a 3rd one to parse the 2nd, etc. Any volunteers? :) BTW, I also have an official grammar representation that I used to get the yacc input for. If that sounds interesting to you, I'll try to dig it up. Bob Rossi