From: Tom de Vries <tdevries@suse.de>
Date: Wed, 13 Oct 2021 09:36:02 +0000 (+0200)
Subject: [gdb/testsuite] Fix gdb.fortran/call-no-debug.exp with native-gdbserver
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=38b03d23c7c7e6a9f8f27a9899fd0a84587c379e;p=binutils-gdb.git

[gdb/testsuite] Fix gdb.fortran/call-no-debug.exp with native-gdbserver

When running test-case gdb.fortran/call-no-debug.exp with target board
native-gdbserver, I run into:
...
(gdb) PASS: gdb.fortran/call-no-debug.exp: print string_func_ (&'abcdefg', 3)
call (integer) string_func_ (&'abcdefg', 3)^M
$2 = 0^M
(gdb) FAIL: gdb.fortran/call-no-debug.exp: call (integer) string_func_ (&'abcdefg', 3)
...

The problem is that gdb_test is used to match inferior output.

Fix this by using gdb_test_stdio.

Tested on x86_64-linux.
---

diff --git a/gdb/testsuite/gdb.fortran/call-no-debug.exp b/gdb/testsuite/gdb.fortran/call-no-debug.exp
index 3c5172e7e36..cbdefb6a7d9 100644
--- a/gdb/testsuite/gdb.fortran/call-no-debug.exp
+++ b/gdb/testsuite/gdb.fortran/call-no-debug.exp
@@ -102,5 +102,7 @@ if { $symbol_name == "" } {
     gdb_test "ptype ${symbol_name}" "type = <unknown return type> \\(\\)"
     gdb_test "print ${symbol_name} (&'abcdefg', 3)" \
 	"'${symbol_name}' has unknown return type; cast the call to its declared return type"
-    gdb_test "call (integer) ${symbol_name} (&'abcdefg', 3)" " abc\r\n\\\$\\d+ = 0"
+    gdb_test_stdio "call (integer) ${symbol_name} (&'abcdefg', 3)" \
+	" abc" \
+	"\\\$\\d+ = 0"
 }