diff options
author | Tom de Vries <tdevries@suse.de> | 2021-11-19 14:33:39 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-11-19 14:33:39 +0100 |
commit | 2e5843d87c4050bf1109921481fb29e1c470827f (patch) | |
tree | b39256f287a4e86605236a1861f32481f15aee1c /opcodes/s390-opc.c | |
parent | 5ee59b4bf20b9109064fda706503628b3e4b2d7a (diff) | |
download | gdb-2e5843d87c4050bf1109921481fb29e1c470827f.zip gdb-2e5843d87c4050bf1109921481fb29e1c470827f.tar.gz gdb-2e5843d87c4050bf1109921481fb29e1c470827f.tar.bz2 |
[gdb/testsuite] Fix gdb.threads/thread-specific-bp.exp
On OBS I ran into a failure in test-case gdb.threads/thread-specific-bp.exp:
...
(gdb) PASS: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
info breakpoint^M
Num Type Disp Enb Address What^M
1 breakpoint keep y 0x0000555555555167 in main at $src:36^M
breakpoint already hit 1 time^M
2 breakpoint keep y 0x0000555555555151 in start at $src:23^M
breakpoint already hit 1 time^M
3 breakpoint keep y 0x0000555555555167 in main at $src:36 thread 2^M
stop only in thread 2^M
4 breakpoint keep y 0x000055555555515c in end at $src:29^M
breakpoint already hit 1 time^M
(gdb) [Thread 0x7ffff7db1640 (LWP 19984) 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: \
thread-specific breakpoint was deleted (timeout)
...
Fix this by waiting for the "[Thread 0x7ffff7db1640 (LWP 19984) exited]"
message before issuing the "info breakpoint command".
Tested on x86_64-linux.
Diffstat (limited to 'opcodes/s390-opc.c')
0 files changed, 0 insertions, 0 deletions