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.
This commit is contained in:
Bruno Larsen 2022-07-20 16:44:31 -03:00
parent e330204945
commit 8a0eb19943

View File

@ -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"