[pushed 0/4] [gdb/testsuite] Fix one more remote host issue in gdb.arch tests

[Tom de Vries <tdevries@suse.de>]

I added REMOTE_HOST_USERNAME in local-remote-host, similar to
REMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost, and when
testing found two failing test-cases in gdb.arch.

The new setup also made clear to me that testing target board
native-stdio-gdbserver in combination with remote host doesn't make sense, so
I've dropped that from my test matrix.  I considered erroring out in the
target board for remote host, but couldn't convince myself that it wouldn't be
overly restrictive.

Tested on x86_64-linux.

Tom de Vries (4):
  [gdb/testsuite] Handle REMOTE_HOST_USERNAME in local-remote-host
  [gdb/testsuite] Fix gdb.arch/i386-biarch-core.exp for remote host
  [gdb/testsuite] Handle remote host in gdb_load_shlib
  [gdb/testsuite] Fix regexp in gdb.arch/ftrace-insn-reloc.exp

 gdb/testsuite/boards/local-remote-host.exp   | 27 +++++++++++++++++---
 gdb/testsuite/gdb.arch/ftrace-insn-reloc.exp |  4 +--
 gdb/testsuite/gdb.arch/i386-biarch-core.exp  |  2 ++
 gdb/testsuite/lib/gdb.exp                    | 26 ++++++++++++++-----
 4 files changed, 48 insertions(+), 11 deletions(-)


base-commit: 3741934fdb04cde6661335e160249f9a83e498a7
-- 
2.35.3