From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24007 invoked by alias); 6 Oct 2004 16:57:30 -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 23992 invoked from network); 6 Oct 2004 16:57:30 -0000 Received: from unknown (HELO sire.mail.pas.earthlink.net) (207.217.120.182) by sourceware.org with SMTP; 6 Oct 2004 16:57:30 -0000 Received: from ip216-26-76-19.dsl.du.teleport.com ([216.26.76.19] helo=stray.canids) by sire.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1CFF6X-0002nF-00 for gdb@sources.redhat.com; Wed, 06 Oct 2004 09:57:29 -0700 Received: from stray.canids (localhost.localdomain [127.0.0.1]) by stray.canids (Postfix) with ESMTP id B1384502AB6 for ; Wed, 6 Oct 2004 09:57:27 -0700 (PDT) From: Felix Lee To: gdb@sources.redhat.com Subject: Re: Bumping MI protocol References: <20041006010100.GA10896@white> <20041006111436.GA11747@white> <01c4ab9d$Blat.v2.2.2$923860c0@zahav.net.il> In-Reply-To: <01c4ab9d$Blat.v2.2.2$923860c0@zahav.net.il> on Wed, 06 Oct 2004 14:10:09 +0200 from "Eli Zaretskii" Date: Wed, 06 Oct 2004 16:57:00 -0000 Message-Id: <20041006165727.B1384502AB6@stray.canids> X-SW-Source: 2004-10/txt/msg00139.txt.bz2 "Eli Zaretskii" : > > From: Bob Rossi > > Exscuse me for being frank, your statements about this question are foolish. > > I, for one, don't think Nathan's comments are foolish. As a volunteer > project, we shouldn't waste too much time discussing hypothetical > issues. I agree with Eli and Nathan, from a different angle. I've never tried implementing a gdb front-end, but if I had to do one, I wouldn't rely on gdb conforming exactly to any particular specification, because bugs happen, and eliminating all bugs is not going to happen in my lifetime. users are unlikely to be happy about restarting a complicated debugging session when they encounter a bug in the debugger, so a robust front-end will need to do some sanity checking of the conversation, and it will also need a method of resynchronizing the conversation when the sanity checks fail. if a front-end has this basic adaptability, then it's not that big a deal if any one-off version of gdb doesn't conform exactly to spec. so you can concentrate effort on making things work well for the versions of gdb that are commonly in use. --