diff options
author | Tom de Vries <tdevries@suse.de> | 2022-10-07 16:17:35 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-10-07 16:17:35 +0200 |
commit | 43792b0de4e1f9cbd7f38c00f7150df66b8bddea (patch) | |
tree | cf3ba73084904eff8d23620778199781fa652be1 | |
parent | 7fe3f841453c46b367aec9a130c3b6e0a580effa (diff) | |
download | gdb-43792b0de4e1f9cbd7f38c00f7150df66b8bddea.zip gdb-43792b0de4e1f9cbd7f38c00f7150df66b8bddea.tar.gz gdb-43792b0de4e1f9cbd7f38c00f7150df66b8bddea.tar.bz2 |
[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.
-rw-r--r-- | gdb/testsuite/lib/gdb.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index d60dcef..99a6de6 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -8636,7 +8636,7 @@ gdb_caching_proc have_mpx { set status [lindex $result 0] set output [lindex $result 1] set status [expr ($status == 0) \ - && ![regexp "^No MPX support\r\n" $output]] + && ![regexp "^No MPX support\r?\n" $output]] remote_file build delete $obj |