aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorBruno Larsen <blarsen@redhat.com>2022-07-20 16:44:31 -0300
committerBruno Larsen <blarsen@redhat.com>2022-09-12 14:07:32 +0200
commit8a0eb1994337e7140715bced108c92db06bef612 (patch)
treedef7e28526d4cdee01fca09a5f4cd231487950b1 /gdb
parente33020494502d0879c418d69d5a2fd6f6453863a (diff)
downloadgdb-8a0eb1994337e7140715bced108c92db06bef612.zip
gdb-8a0eb1994337e7140715bced108c92db06bef612.tar.gz
gdb-8a0eb1994337e7140715bced108c92db06bef612.tar.bz2
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.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/gdb.base/info-program.exp6
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/testsuite/gdb.base/info-program.exp b/gdb/testsuite/gdb.base/info-program.exp
index facc13e..1dc470b 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"