diff options
| author | Pedro Alves <palves@redhat.com> | 2017-10-24 23:22:56 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2017-10-24 23:22:56 +0100 |
| commit | 792ccf005f391f46e295e250f285d040ab105ab7 (patch) | |
| tree | 4f3f5f8ecf4f74bc29140e180709133cd1b6bf7c /gdb/ctf.c | |
| parent | 63a25ea0de6d2f6d45b26af8d9c808aa35962256 (diff) | |
| download | binutils-792ccf005f391f46e295e250f285d040ab105ab7.zip binutils-792ccf005f391f46e295e250f285d040ab105ab7.tar.gz binutils-792ccf005f391f46e295e250f285d040ab105ab7.tar.bz2 | |
Fix racy test in gdb.base/new-ui.exp
I noticed gdb.base/new-ui.exp failing once here with:
FAIL: gdb.base/new-ui.exp: do_test: delete all breakpoints on extra console (got interactive prompt)
FAIL: gdb.base/new-ui.exp: do_test: main console: next causes no spurious output on other console
FAIL: gdb.base/new-ui.exp: do_test: main console: breakpoint hit reported on other console
The problem is 100% reproducible with check-read1:
$ make check-read1 TESTS="gdb.*/new-ui.exp"
testsuite/gdb.log shows:
delete
Delete all breakpoints? (y or n) [answered Y; input not from terminal]
(gdb) FAIL: gdb.base/new-ui.exp: do_test: delete all breakpoints on extra console (got interactive prompt)
This commit fixes the problem.
gdb/testsuite/ChangeLog:
2017-10-24 Pedro Alves <palves@redhat.com>
* gdb.base/new-ui.exp (do_test): Split "delete all breakpoints on
extra console" test in two stages.
Diffstat (limited to 'gdb/ctf.c')
0 files changed, 0 insertions, 0 deletions