public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: rename source file gdb.debuginfod/main.c Date: Fri, 18 Nov 2022 11:46:42 +0000 (GMT) [thread overview] Message-ID: <20221118114642.92DFF384F487@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=59d6ca65f5e29a110be55f5057c710e29527e229 commit 59d6ca65f5e29a110be55f5057c710e29527e229 Author: Andrew Burgess <aburgess@redhat.com> Date: Thu Nov 17 11:11:13 2022 +0000 gdb/testsuite: rename source file gdb.debuginfod/main.c The test gdb.debuginfod/fetch_src_and_symbols.exp uses a source file named main.c. I can't see any particular reason why the file is named as such. Usually test source files are named after the test script. This commit just renames the source file inline with the test script, and updates the call to standard_testfile (removing the reference to main.c). There's no particular reason for this change other than seeing the file named main.c made me thing that the source file must be shared with some other test (it isn't). There should be no change in what is tested after this commit. Diff: --- gdb/testsuite/gdb.debuginfod/{main.c => fetch_src_and_symbols.c} | 0 gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/gdb/testsuite/gdb.debuginfod/main.c b/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.c similarity index 100% rename from gdb/testsuite/gdb.debuginfod/main.c rename to gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.c diff --git a/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp b/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp index b57b3201cf7..8b3c2cf709e 100644 --- a/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp +++ b/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp @@ -15,7 +15,7 @@ # Test debuginfod functionality -standard_testfile main.c +standard_testfile load_lib dwarf.exp load_lib debuginfod-support.exp
reply other threads:[~2022-11-18 11:46 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=20221118114642.92DFF384F487@sourceware.org \ --to=aburgess@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).