Make default_mi_gdb_start/dbx_gdb_start use gdb_spawn
authorPedro Alves <pedro@palves.net>
Sun, 13 Sep 2020 19:31:25 +0000 (20:31 +0100)
committerPedro Alves <pedro@palves.net>
Sun, 13 Sep 2020 19:31:25 +0000 (20:31 +0100)
commit2f4b83cd51953fdf9626dc7a198b35505d1f5472
treea88028733218de22e23db0d0025bb6363c8984d0
parentc49da0e466e1bcb6e1f363ea4a806cfd2c322cb0
Make default_mi_gdb_start/dbx_gdb_start use gdb_spawn

If a board file wants to customize how gdb is launched, the obvious
way is to have the board override gdb_spawn.  However, that doesn't
work for either gdb.mi/ testcases or gdb.base/dbx.exp, because
default_mi_gdb_start and dbx_gdb_start don't use gdb_spawn currently.

That is fixed by this patch.

gdb/testsuite/

* gdb.base/dbx.exp (dbx_gdb_start): Adjust to use gdb_spawn
instead of spawning GDB with remote_spawn.
* lib/mi-support.exp (default_mi_gdb_start): Adjust to use
gdb_spawn instead of spawning GDB with remote_spawn.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/dbx.exp
gdb/testsuite/lib/mi-support.exp