diff options
| author | Pedro Alves <palves@redhat.com> | 2015-11-30 16:05:12 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-11-30 18:36:30 +0000 |
| commit | f015c27b5294eaf87d0aa814d94972e65c7cc90e (patch) | |
| tree | aa5d583a72d54ff1957a04c777130303e114cc5b /COPYING3 | |
| parent | 01a49af81b74c425baf1215760d50889bd68f27c (diff) | |
| download | gdb-f015c27b5294eaf87d0aa814d94972e65c7cc90e.zip gdb-f015c27b5294eaf87d0aa814d94972e65c7cc90e.tar.gz gdb-f015c27b5294eaf87d0aa814d94972e65c7cc90e.tar.bz2 | |
Fix mi-nonstop.exp with extended-remote
Testing with "maint set target-non-stop on" makes mi-nonstop.exp run
with the extended-remote board. That reveals that mi-nonstop.exp is
using the wrong predicate to check for "using remote protocol".
This is not visible today because non-stop tests all fail to run with
extended-remote board, because they spawn gdb and then do "set
non-stop on". However, with that board, gdb connects to the gdbserver
from within mi_gdb_start, and changing non-stop when already connected
doesn't work. Fix that by instead enabling non-stop mode on gdb's
command line.
gdb/testsuite/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* gdb.mi/mi-nonstop.exp: Append "set non-stop on" to GDBFLAGS
instead of issuing "-gdb-set non-stop 1" after starting gdb.
Use mi_is_target_remote instead of checking "is_remote target".
* lib/gdb.exp (gdb_is_target_remote): Rename to ...
(gdb_is_target_remote_prompt): ... this, and add 'prompt_regexp'
parameter.
(gdb_is_target_remote): Reimplement.
* lib/mi-support.exp (mi_is_target_remote): New procedure.
Diffstat (limited to 'COPYING3')
0 files changed, 0 insertions, 0 deletions