[binutils-gdb] update gdb.base/info-program.exp to not fail with clang

[Bruno Larsen]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8a0eb1994337e7140715bced108c92db06bef612

commit 8a0eb1994337e7140715bced108c92db06bef612
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Wed Jul 20 16:44:31 2022 -0300

    update gdb.base/info-program.exp to not fail with clang
    
    The test specifically mentions that it doesn't care where the program
    stops, however it was still testing for a specific location.  The clang
    compiler emits different line information for epilogue, so GDB reports a
    different stopping location, depending on the used compiler.  With this
    patch the test works even with clang.

Diff:
---
 gdb/testsuite/gdb.base/info-program.exp | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gdb/testsuite/gdb.base/info-program.exp b/gdb/testsuite/gdb.base/info-program.exp
index facc13efa2f..1dc470b6e79 100644
--- a/gdb/testsuite/gdb.base/info-program.exp
+++ b/gdb/testsuite/gdb.base/info-program.exp
@@ -26,9 +26,9 @@ if { ![runto_main] } {
 gdb_test "info program" "Program stopped at $hex\.\r\nIt stopped at breakpoint $decimal\.\r\nType \"info stack\" or \"info registers\" for more information\." \
     "info program after run to main"
 
-# We don't really care where this step lands, so long as it gets
-# the inferior pushed off the breakpoint it's currently on...
-gdb_test "next" "$decimal\t.*" "step before info program"
+# We don't really care where this step lands, so long as GDB reports
+# that the inferior stopped  due to a step in the subsequent test.
+gdb_test "next" ".*" "step before info program"
 
 gdb_test "info program" "Program stopped at $hex\.\r\nIt stopped after being stepped\.\r\nType \"info stack\" or \"info registers\" for more information\." \
     "info program after next"