Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [committed testsuite patch] auxv.exp cascading failures
Date: Sat, 05 Jun 2004 00:11:00 -0000	[thread overview]
Message-ID: <200406050011.i550B8oj023262@magilla.sf.frob.com> (raw)
In-Reply-To: Michael Elizabeth Chastain's message of  Friday, 4 June 2004 19:44:09 -0400 <20040604234409.146364B104@berman.michael-chastain.com>

I've replaced it with this different patch instead.


Thanks,
Roland


2004-06-04  Roland McGrath  <roland@redhat.com>

	* gdb.base/auxv.exp (fetch_auxv): Revert last change and fix it
	differently to be robust to output buffering differences.

--- auxv.exp.~1.1.~	2004-03-16 13:39:57.000000000 -0800
+++ auxv.exp	2004-06-04 17:07:08.000000000 -0700
@@ -82,12 +82,15 @@ proc fetch_auxv {test} {
 	}
 	-ex "The program has no auxiliary information now" {
 	    set bad 1
+	    exp_continue
 	}
 	-ex "Auxiliary vector is empty" {
 	    set bad 1
+	    exp_continue
 	}
 	-ex "No auxiliary vector found" {
 	    set bad 1
+	    exp_continue
 	}
 	-re "^\[0-9\]+\[ \t\]+(AT_\[^ \t\]+)\[^\r\n\]+\[\r\n\]+" {
 	    lappend auxv_lines $expect_out(0,string)
@@ -103,9 +106,12 @@ proc fetch_auxv {test} {
 	    incr bad
 	}
 	-re "^\[^\r\n\]+\[\r\n\]+" {
+	    if {!$bad} {
 	    warning "Unrecognized output: $expect_out(0,string)"
 	    set bad 1
 	}
+	    exp_continue
+	}
     }] != 0} {
 	return {}
     }


  reply	other threads:[~2004-06-05  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 23:44 Michael Elizabeth Chastain
2004-06-05  0:11 ` Roland McGrath [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-04 21:37 Roland McGrath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406050011.i550B8oj023262@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox