[gdb/testsuite] Fix gdb.mi/*.exp with remote-gdbserver-on-localhost
authorTom de Vries <tdevries@suse.de>
Tue, 7 Mar 2023 08:59:56 +0000 (09:59 +0100)
committerTom de Vries <tdevries@suse.de>
Tue, 7 Mar 2023 08:59:56 +0000 (09:59 +0100)
commite8850b52624245a1d7b8ef9fc41abb6175ec74e4
treef2f41add62abe1907f48f099f7701a489d9f822f
parent07f285934886016ddd82cac99a3873e68b499d5c
[gdb/testsuite] Fix gdb.mi/*.exp with remote-gdbserver-on-localhost

When running test-cases gdb.mi/*.exp with target board
remote-gdbserver-on-localhost, we run into a few fails.

Fix these (and make things more similar to the gdb.exp procs) by:
- factoring out mi_load_shlib out of mi_load_shlibs
- making mi_load_shlib use gdb_download_shlib, like
  gdb_load_shlib
- factoring out mi_locate_shlib out of mi_load_shlib
- making mi_locate_shlib check for mi_spawn_id, like
  gdb_locate_shlib
- using gdb_download_shlib and mi_locate_shlib in the test-cases.

Tested on x86_64-linux, with and without target board
remote-gdbserver-on-localhost.
gdb/testsuite/gdb.mi/mi-catch-load.exp
gdb/testsuite/gdb.mi/mi-var-invalidate-shlib.exp
gdb/testsuite/lib/mi-support.exp