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

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