diff options
| author | Pedro Alves <pedro@palves.net> | 2020-09-13 20:31:25 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2020-09-13 20:31:25 +0100 |
| commit | 2f4b83cd51953fdf9626dc7a198b35505d1f5472 (patch) | |
| tree | a88028733218de22e23db0d0025bb6363c8984d0 /gdb/python/py-function.c | |
| parent | c49da0e466e1bcb6e1f363ea4a806cfd2c322cb0 (diff) | |
| download | binutils-2f4b83cd51953fdf9626dc7a198b35505d1f5472.zip binutils-2f4b83cd51953fdf9626dc7a198b35505d1f5472.tar.gz binutils-2f4b83cd51953fdf9626dc7a198b35505d1f5472.tar.bz2 | |
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.
Diffstat (limited to 'gdb/python/py-function.c')
0 files changed, 0 insertions, 0 deletions