From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17459 invoked by alias); 6 Jan 2005 01:36:12 -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 17427 invoked from network); 6 Jan 2005 01:36:03 -0000 Received: from unknown (HELO rwcrmhc11.comcast.net) (204.127.198.35) by sourceware.org with SMTP; 6 Jan 2005 01:36:03 -0000 Received: from [10.0.1.2] (h000393256f12.ne.client2.attbi.com[24.61.199.96]) by comcast.net (rwcrmhc11) with SMTP id <2005010601360101300dd957e>; Thu, 6 Jan 2005 01:36:02 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Thu, 06 Jan 2005 01:36:00 -0000 Subject: Re: GDB/MI Output Syntax From: Paul Schlie To: Bob Rossi CC: Message-ID: In-Reply-To: <20050106011036.GA27670@white> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2005-01/txt/msg00048.txt.bz2 Understood. > I understand your point here. Here's the state of affair's as far as I > see it > > I want to write a curses based front end to GDB. I looked at the > alternatives for communicating with GDB and found that MI was the > documented way to do this. So, with that in mind I started to look for a > parser and grammar and none were found. This frustrated me cause i > didn't want to write one, so I suggested GDB output XML. Everyone > hated this idea. So, I decided to write the parser that everyone else > could use from here on out, so no one would have to reinvent the wheel. > > I've already put some effort into the MI and this is the point that I'm > currently at. The goal I'm shooting for is to use this parser to really > validate the output of the MI. Better than is being done know. Make sure > the syntax and the semantics are perfect. > > Basically, I'm not looking into writing a whole new frame work for > communicating with GDB, I just want to improve what's already there. > > Thanks, > Bob Rossi