Pedro Alves 5ed7a928ac Fix racy output matching in gdb.base/multi-attach.exp, gdb.server/ext-{attach, restart, ext-run}.exp ...

This commit fixes this same problem in several places:

  (gdb) PASS: gdb.multi/multi-attach.exp: backtrace 2
  kill
  Kill the program being debugged? (y or n) y
  (gdb) FAIL: gdb.multi/multi-attach.exp: kill inferior 2 (got interactive prompt)

This is just another case of the gdb_test_multiple's internal "got
interactive prompt" pattern matching because the testcase misses
matching enough.

gdb/testsuite/ChangeLog:
2017-11-09  Pedro Alves  <palves@redhat.com>

	* gdb.multi/multi-attach.exp ("kill" test): Match the whole query
	output.
	* gdb.server/ext-attach.exp ("kill" test): Likewise.
	* gdb.server/ext-restart.exp ("kill" test): Likewise.
	* gdb.server/ext-run.exp ("kill" test): Likewise.
	* gdb.server/ext-wrapper.exp ("kill" test): Likewise.

2017-11-09 22:46:44 +00:00

..

base.exp

…

bkpt-multi-exec.c

…

bkpt-multi-exec.exp

Skip a few tests on targets that can't use the "run" commmand.

2017-10-13 18:11:31 +01:00

crashme.c

…

dummy-frame-restore.c

…

dummy-frame-restore.exp

…

goodbye.c

…

hangout.c

…

hello.c

…

info-threads.exp

…

multi-arch-exec.c

Multi-arch exec, more register reading avoidance

2017-10-09 18:11:01 +01:00

multi-arch-exec.exp

gdb.multi/multi-arch-exec.exp: Also test -m32 => -m64

2017-10-09 18:11:02 +01:00

multi-arch.exp

…

multi-attach.c

…

multi-attach.exp

Fix racy output matching in gdb.base/multi-attach.exp, gdb.server/ext-{attach, restart, ext-run}.exp

2017-11-09 22:46:44 +00:00

remove-inferiors.c

…

remove-inferiors.exp

…

tids.c

…

tids.exp

…

watchpoint-multi-exit.c

…

watchpoint-multi-exit.exp

…

watchpoint-multi.c

…

watchpoint-multi.exp

…