Re: Fully anchor mi_gdb_test expected results.

[Daniel Jacobowitz <drow@false.org>]

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