Handle additional connection error

On Ubuntu 18.04/20.04 I was running into annoying timeouts for
gdb.server/server-connect.exp. Those were caused by the ipv6 tests, because
they were running into the "Cannot assign requested address" error, originated
from the connect syscall.

Improve this by handling this additional error in the testsuite library.

It still fails for me, but at least it fails pretty quickly and doesn't make the
testsuite run take longer.

gdb/testsuite/ChangeLog:

2021-01-21  Luis Machado  <luis.machado@linaro.org>

	* lib/gdbserver-support.exp (gdb_target_cmd_ext): Handle a new error
	message.
This commit is contained in:
Luis Machado
2021-01-21 16:09:07 -03:00
parent d5d24e12f9
commit cd211c75cb
2 changed files with 8 additions and 0 deletions

View File

@ -1,3 +1,8 @@
2021-01-21 Luis Machado <luis.machado@linaro.org>
* lib/gdbserver-support.exp (gdb_target_cmd_ext): Handle a new error
message.
2021-01-21 Simon Marchi <simon.marchi@polymtl.ca>
* lib/tuiterm.exp (_log, _log_cur): New, use throughout.

View File

@ -64,6 +64,9 @@ proc gdb_target_cmd_ext { targetname serialport {additional_text ""} } {
-re "Couldn't establish connection to remote.*$gdb_prompt $" {
verbose "Connection failed"
}
-re "Cannot assign requested address.*$gdb_prompt $" {
verbose "Could not assign requested address"
}
-re "Non-stop mode requested, but remote does not support non-stop.*$gdb_prompt $" {
verbose "remote does not support non-stop"
return 1