[gdb/testsuite] Handle output after prompt in gdb.threads/step-N-all-progress.exp
commit3d053417ea7140c3b3a684fcf9edf24abdfa68fd
authorTom de Vries <tdevries@suse.de>
Wed, 7 Jun 2023 09:36:19 +0000 (7 11:36 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 7 Jun 2023 09:36:19 +0000 (7 11:36 +0200)
treee7746f0e8907cbeb9d3ac18126b6b0382c97edfb
parentc6cad198b15e90df947921b58a0f052635050b4d
[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.
gdb/testsuite/gdb.threads/step-N-all-progress.exp