diff options
| author | Pedro Alves <palves@redhat.com> | 2017-11-09 22:44:09 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2017-11-09 22:46:44 +0000 |
| commit | 5ed7a928acc231ccd13af71cf6df9900250cf884 (patch) | |
| tree | 7220ddce8f1786ed7e496303d81ef29c732f30e0 /gdb/target-float.c | |
| parent | a60e07381c812ab82aff9abae203fd192f460ef4 (diff) | |
| download | gdb-5ed7a928acc231ccd13af71cf6df9900250cf884.zip gdb-5ed7a928acc231ccd13af71cf6df9900250cf884.tar.gz gdb-5ed7a928acc231ccd13af71cf6df9900250cf884.tar.bz2 | |
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.
Diffstat (limited to 'gdb/target-float.c')
0 files changed, 0 insertions, 0 deletions