diff options
author | Yao Qi <yao.qi@linaro.org> | 2017-04-05 14:46:13 +0100 |
---|---|---|
committer | Yao Qi <yao.qi@linaro.org> | 2017-04-05 14:46:13 +0100 |
commit | 55a98976756cb2df83ac8f8e9799331fbcc4f669 (patch) | |
tree | c9eedaad451114989c2562d3517d002a03e2ca1f /gdb/macroexp.c | |
parent | 8dea77f0254d6a76d71092c922e9409ef1b67df4 (diff) | |
download | binutils-55a98976756cb2df83ac8f8e9799331fbcc4f669.zip binutils-55a98976756cb2df83ac8f8e9799331fbcc4f669.tar.gz binutils-55a98976756cb2df83ac8f8e9799331fbcc4f669.tar.bz2 |
Fix racy test in gdb.threads/thread-specific-bp.exp
I see the following test fail from time to time, due to the racy test
in gdb.threads/thread-specific-bp.exp.
continue -a^M
Continuing.^M
^M
Thread 1 "thread-specific" hit Breakpoint 4, end () at binutils-gdb/gdb/testsuite/gdb.threads/thread-specific-bp.c:29^M
29 }^M
(gdb) [Thread 0x40322460 (LWP 12950) exited]^M
Thread-specific breakpoint 3 deleted - thread 2 no longer in the thread list.^M
FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
This patch changes gdb_test to gdb_test_multiple to match prompt only
instead of both prompt and anchor.
gdb/testsuite:
2017-04-05 Yao Qi <yao.qi@linaro.org>
* gdb.threads/thread-specific-bp.exp (check_thread_specific_breakpoint):
Use gdb_test_multiple, and don't match anchor.
Diffstat (limited to 'gdb/macroexp.c')
0 files changed, 0 insertions, 0 deletions