[gdb/testsuite] Fix have_mpx with remote-gdbserver-on-localhost
authorTom de Vries <tdevries@suse.de>
Fri, 7 Oct 2022 14:17:35 +0000 (16:17 +0200)
committerTom de Vries <tdevries@suse.de>
Fri, 7 Oct 2022 14:17:35 +0000 (16:17 +0200)
commit43792b0de4e1f9cbd7f38c00f7150df66b8bddea
treecf3ba73084904eff8d23620778199781fa652be1
parent7fe3f841453c46b367aec9a130c3b6e0a580effa
[gdb/testsuite] Fix have_mpx with remote-gdbserver-on-localhost

With target board remote-gdbserver-on-localhost and gdb.arch/i386-mpx-call.exp
I run into:
...
FAIL: gdb.arch/i386-mpx-call.exp: upper_bnd0: continue to a bnd violation
...

This is due to the have_mpx test which should return 0, but instead returns 1
because the captured output:
...
No MPX support
No MPX support
...
does not match the used regexp:
...
    set status [expr ($status == 0) \
                   && ![regexp "^No MPX support\r\n" $output]]
...
which does match the captured output with native:
...
No MPX support^M
No MPX support^M
...

Fix this by making the \r in the regexp optional.

Tested on x86_64-linux, with native and target board
remote-gdbserver-on-localhost.
gdb/testsuite/lib/gdb.exp