public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] update gdb.base/info-program.exp to not fail with clang Date: Mon, 12 Sep 2022 12:17:58 +0000 (GMT) [thread overview] Message-ID: <20220912121758.78F313857004@sourceware.org> (raw) 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"
reply other threads:[~2022-09-12 12:17 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220912121758.78F313857004@sourceware.org \ --to=blarsen@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).