diff options
| author | Tom de Vries <tdevries@suse.de> | 2023-06-07 11:36:19 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2023-06-07 11:36:19 +0200 |
| commit | 3d053417ea7140c3b3a684fcf9edf24abdfa68fd (patch) | |
| tree | e7746f0e8907cbeb9d3ac18126b6b0382c97edfb /libiberty/timeval-utils.c | |
| parent | c6cad198b15e90df947921b58a0f052635050b4d (diff) | |
| download | gdb-3d053417ea7140c3b3a684fcf9edf24abdfa68fd.zip gdb-3d053417ea7140c3b3a684fcf9edf24abdfa68fd.tar.gz gdb-3d053417ea7140c3b3a684fcf9edf24abdfa68fd.tar.bz2 | |
[gdb/testsuite] Handle output after prompt in gdb.threads/step-N-all-progress.exp
Using "taskset -c 0" I run into this timeout:
...
(gdb) PASS: gdb.threads/step-N-all-progress.exp: non-stop=on: \
target-non-stop=on: continue to breakpoint: break here
next 3^M
[New Thread 0x7ffff7dbd6c0 (LWP 10202)]^M
50 return 0;^M
(gdb) [Thread 0x7ffff7dbd6c0 (LWP 10202) exited]^M
FAIL: gdb.threads/step-N-all-progress.exp: non-stop=on: target-non-stop=on: \
next 3 (timeout)
...
The problem is that this test:
...
gdb_test "next 3" "return 0;"
...
expects no output after the prompt.
Fix this by using -no-prompt-anchor.
Tested on x86_64-linux.
Diffstat (limited to 'libiberty/timeval-utils.c')
0 files changed, 0 insertions, 0 deletions