From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4593 invoked by alias); 1 Feb 2005 14:39:24 -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 4503 invoked from network); 1 Feb 2005 14:39:16 -0000 Received: from unknown (HELO lakermmtao08.cox.net) (68.230.240.31) by sourceware.org with SMTP; 1 Feb 2005 14:39:16 -0000 Received: from white ([68.9.64.121]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050201143916.ZKAH29855.lakermmtao08.cox.net@white> for ; Tue, 1 Feb 2005 09:39:16 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1CvzBV-0002cU-00 for ; Tue, 01 Feb 2005 09:39:17 -0500 Date: Tue, 01 Feb 2005 14:39:00 -0000 From: Bob Rossi To: GDB Subject: Re: How do I get regexp from expect at gdb_expect? Message-ID: <20050201143917.GB9962@white> Mail-Followup-To: GDB References: <20050131150652.GA7955@white> <20050131162609.GA19459@nevyn.them.org> <20050131211042.GA8411@white> <20050131212122.GA10092@nevyn.them.org> <20050131220050.GB8411@white> <20050131220354.GA11955@nevyn.them.org> <20050131221247.GC8411@white> <20050201035236.GA24182@nevyn.them.org> <20050201142008.GA9962@white> <20050201142315.GA18652@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050201142315.GA18652@nevyn.them.org> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-02/txt/msg00003.txt.bz2 On Tue, Feb 01, 2005 at 09:23:15AM -0500, Daniel Jacobowitz wrote: > On Tue, Feb 01, 2005 at 09:20:08AM -0500, Bob Rossi wrote: > > Could we have GDB turn off echo'ing with an MI command. > > > > -mi-disable-echo > > > > I think that would fix this entire problem. > > I don't think there's a problem to be fixed; and it wouldn't "fix" > anything, since you'd still have to go through the testsuite, add > leading anchors, and make sure any other messages were handled. Plus > it would mean teaching the MI driver to mess with terminal modes. Well, I'm trying to take testing the output of the MI testsuite to the next level. Instead of just matching regular expressions, and letting any output from GDB before the "match" get by, I'm trying to match only output that has the correct MI output syntax. Unfortunately, as of know, there are 2 holes in the testsuite that I have found so far. The first is that Expect also matches the "echoed" data. This data isn't even seen by real front end clients, and, it's not even really the output of GDB. So this data must be removed from the output stream if the syntax of the MI command is going to be validated. Second, it looks as if extra data could come out of GDB, and still pass the testsuite. This certainly would stop me from validating the syntax, since, there would be no point in validating only 9/10 of the output of an MI output command. Also, if GDB was outputting some extra data, front end clients would most likely break, while the testsuite could continue passing just fine. I would do the work of adding, the leading anchors and making sure all other loose ends were tied up. With all of this in mind, does disabling the 'echoing' of the terminal sound reasonable? Thanks, Bob Rossi