[gdb/testsuite] Fix gdb.multi/attach-no-multi-process.exp with check-readmore
authorTom de Vries <tdevries@suse.de>
Sun, 1 May 2022 16:06:44 +0000 (18:06 +0200)
committerTom de Vries <tdevries@suse.de>
Sun, 1 May 2022 16:06:44 +0000 (18:06 +0200)
commit94afbc7b1b27f03974133b3d620470e9725a21df
tree7b8c74622b8ea3b1f346948d5dabe9d5360678d7
parente9c5fe2f40e7da0f104624ee81c9720a7956e64c
[gdb/testsuite] Fix gdb.multi/attach-no-multi-process.exp with check-readmore

When running test-case gdb.multi/attach-no-multi-process.exp with
check-readmore, I get:
...
(gdb) attach 13411^M
Attaching to Remote target^M
No unwaited-for children left.^M
(gdb) Reading symbols from attach-no-multi-process...^M
Reading symbols from /lib64/libm.so.6...^M
(No debugging symbols found in /lib64/libm.so.6)^M
Reading symbols from /lib64/libc.so.6...^M
(No debugging symbols found in /lib64/libc.so.6)^M
Reading symbols from /lib64/ld-linux-x86-64.so.2...^M
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)^M
0x00007f5df1fffc8a in clock_nanosleep@GLIBC_2.2.5 () from /lib64/libc.so.6^M
FAIL: gdb.multi/attach-no-multi-process.exp: target_non_stop=off: \
  attach to the program via remote (timeout)
...

The problem is that the attach output is matched using gdb_test, which uses
the '$gdb_prompt $' regexp, and this does not handle the case that '(gdb) ' is
not the last available output.

Fix this by using a gdb_test_multiple instead with a '$gdb_prompt ' regexp, so
without the '$' anchor.

Tested on x86_64-linux with native, check-read1 and check-readmore.
gdb/testsuite/gdb.multi/attach-no-multi-process.exp