Expect for another variant of error message when gdbserver cannot resolve hostname
authorSergio Durigan Junior <sergiodj@redhat.com>
Fri, 13 Jul 2018 20:20:34 +0000 (16:20 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Fri, 13 Jul 2018 20:20:34 +0000 (16:20 -0400)
commit7f1f7e23939adc7d71036a17fc6081e3af7ca585
treeacdd48c05850bb48888b4c4e7e4ad97bc377c9ab
parent027a4c30d03e3f434ddfa61e7f026e3b15f83daa
Expect for another variant of error message when gdbserver cannot resolve hostname

I've noticed that on a few hosts, when given an invalid hostname,
gdbserver fails with:

  spawn /../../gdb/gdbserver/gdbserver --once tcp8:123:2353 /gdb/build/fedora-s390x/build/gdb/testsuite/outputs/gdb.server/server-connect/server-connect
  tcp8:123:2353: cannot resolve name: No address associated with hostname
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Exiting

Unfortunately, this causes a fail on the new
gdb.server/server-connect.exp test (introduced by the IPv6 patch):

  FAIL: gdb.server/server-connect.exp: tcp8: start gdbserver: gdbserver should fail but did not

This happens because we're expecting for another variant of this error
message:

  cannot resolve name: Name or service not known

Therefore, this patch extends the helper function 'gdbserver_start' to
also recognize the "No address associated with hostname" message.
This "fixes" the testcase on the hosts that use this variant.

gdb/testsuite/ChangeLog:
2018-07-13  Sergio Durigan Junior  <sergiodj@redhat.com>

* lib/gdbserver-support.exp (gdbserver_start): Expect for the
message "No address associated with hostname" when gdbserver
cannot resolve the hostname.
gdb/testsuite/ChangeLog
gdb/testsuite/lib/gdbserver-support.exp