From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16813 invoked by alias); 18 Sep 2005 01:32:30 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16533 invoked by uid 22791); 18 Sep 2005 01:31:56 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 18 Sep 2005 01:31:56 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1EGo27-0008U2-1c for gdb-patches@sources.redhat.com; Sat, 17 Sep 2005 21:31:55 -0400 Date: Sun, 18 Sep 2005 01:32:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: Fully anchor mi_gdb_test expected results. Message-ID: <20050918013154.GR8777@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <20050804140937.GB4054@white> <20050804141750.GA11536@nevyn.them.org> <20050804142601.GC4054@white> <20050804143238.GA11996@nevyn.them.org> <20050804203704.GA4472@white> <20050804205747.GA22030@nevyn.them.org> <20050804211834.GD4472@white> <20050804224044.GB4931@white> <20050804224351.GA25174@nevyn.them.org> <20050804234959.GC4931@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050804234959.GC4931@white> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-09/txt/msg00143.txt.bz2 On Thu, Aug 04, 2005 at 07:49:59PM -0400, Bob Rossi wrote: > On Thu, Aug 04, 2005 at 06:43:51PM -0400, Daniel Jacobowitz wrote: > > On Thu, Aug 04, 2005 at 06:40:44PM -0400, Bob Rossi wrote: > > > Here are my testsuite results. The first one looks like a bug I > > > introduced, and the others look like random thread pass/failures. Is > > > that correct? > > > > Yes. Does removing two backslashes in sizeof.exp fix it? They > > shouldn't have been there at all. > > Geez Daniel, thanks for all the help. Here is the patch that plays > nicely with the testsuite. I captured both the MI input command and the > MI output command. Eventually testing can be done on the MI input > command also. Hi Bob, I don't remember - what's the status of this patch? I think there were no more problems with it. I'm a bit curious about this though: > + -re "^(.*$string_regex.*)($pattern\[\r\n\]+$mi_gdb_prompt\[ \]*)$" { > + # At this point, $expect_out(1,string) is the MI input command. > + # and $expect_out(2,string) is the MI output command. Seems like the .*'s there are really defeating the point of anchoring it! -- Daniel Jacobowitz CodeSourcery, LLC