Blame SOURCES/gdb-rhbz881849-ipv6-2of3.patch

190f2a
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
190f2a
From: Sergio Durigan Junior <sergiodj@redhat.com>
190f2a
Date: Mon, 30 Jul 2018 15:23:27 -0400
190f2a
Subject: gdb-rhbz881849-ipv6-2of3.patch
190f2a
190f2a
Match any kind of error after "cannot resolve name" on lib/gdbserver-support.exp:gdbserver_start
190f2a
190f2a
On commit:
190f2a
190f2a
commit 7f1f7e23939adc7d71036a17fc6081e3af7ca585
190f2a
Author: Sergio Durigan Junior <sergiodj@redhat.com>
190f2a
Date:   Fri Jul 13 16:20:34 2018 -0400
190f2a
190f2a
    Expect for another variant of error message when gdbserver cannot resolve hostname
190f2a
190f2a
I extended the regular expression being used to identify whether
190f2a
gdbserver could not resolve a (host)name.  This was needed because the
190f2a
error message being printed had a different variation across some
190f2a
systems.  However, as it turns out, I've just noticed that the message
190f2a
has yet another variation:
190f2a
190f2a
  target remote tcp8:123:2353
190f2a
  tcp8:123:2353: cannot resolve name: System error
190f2a
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
190f2a
  tcp8:123:2353: No such file or directory.
190f2a
  (gdb) FAIL: gdb.server/server-connect.exp: tcp8: connect to gdbserver using tcp8:123
190f2a
190f2a
which is causing FAILs on some systems (namely, Fedora-i686 on
190f2a
BuildBot).
190f2a
190f2a
So instead of trying to predict everything that can be printed, I
190f2a
decided to just match anything after the "cannot resolve name: " part.
190f2a
This patch implements that.
190f2a
190f2a
Regression tested on the BuildBot.
190f2a
190f2a
gdb/testsuite/ChangeLog:
190f2a
2018-07-30  Sergio Durigan Junior  <sergiodj@redhat.com>
190f2a
190f2a
	* lib/gdbserver-support.exp (gdbserver_start): Match any kind of
190f2a
	error after "cannot resolve name" string.
190f2a
190f2a
diff --git a/gdb/testsuite/lib/gdbserver-support.exp b/gdb/testsuite/lib/gdbserver-support.exp
190f2a
--- a/gdb/testsuite/lib/gdbserver-support.exp
190f2a
+++ b/gdb/testsuite/lib/gdbserver-support.exp
190f2a
@@ -326,7 +326,7 @@ proc gdbserver_start { options arguments } {
190f2a
 		    continue
190f2a
 		}
190f2a
 	    }
190f2a
-	    -re ".*: cannot resolve name: Name or service not known\r\n" {
190f2a
+	    -re ".*: cannot resolve name: .*\r\n" {
190f2a
 		error "gdbserver cannot resolve name."
190f2a
 	    }
190f2a
 	    timeout {