[gdb/testsuite] Fix gdb.fortran/call-no-debug.exp with native-gdbserver
authorTom de Vries <tdevries@suse.de>
Wed, 13 Oct 2021 09:36:02 +0000 (11:36 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 13 Oct 2021 09:36:02 +0000 (11:36 +0200)
commit38b03d23c7c7e6a9f8f27a9899fd0a84587c379e
tree4f6454691ffac38a05077f5e0e34b6bf3ab5fc57
parent2786ef85faf16c13029548832c4e4b025bf2624c
[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.
gdb/testsuite/gdb.fortran/call-no-debug.exp