From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>, Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 1/2] gdb/testsuite: rename source file gdb.debuginfod/main.c
Date: Thu, 17 Nov 2022 11:38:05 +0000 [thread overview]
Message-ID: <fd18571a140245d1151e824ac324a784dfb89b28.1668684812.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1668684812.git.aburgess@redhat.com>
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.
---
.../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(-)
rename gdb/testsuite/gdb.debuginfod/{main.c => fetch_src_and_symbols.c} (100%)
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
--
2.25.4
next prev parent reply other threads:[~2022-11-17 11:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 16:36 [PATCH 0/6] The DWARF assembler and Clang Andrew Burgess
2022-11-11 16:36 ` [PATCH 1/6] gdb/testsuite: don't avoid DWARF assembler tests with Clang Andrew Burgess
2022-11-11 16:36 ` [PATCH 2/6] gdb/testsuite: fix gdb.trace/unavailable-dwarf-piece.exp " Andrew Burgess
2022-11-16 14:41 ` Bruno Larsen
2022-11-17 11:06 ` Andrew Burgess
2022-12-12 17:55 ` Tom Tromey
2022-12-13 15:39 ` Andrew Burgess
2022-11-11 16:36 ` [PATCH 3/6] gdb/testsuite: fix gdb.compile/compile-ops.exp with clang Andrew Burgess
2022-11-16 16:27 ` Tom Tromey
2022-11-11 16:36 ` [PATCH 4/6] gdb/testsuite: add (and use) a new build-id compile option Andrew Burgess
2022-11-11 16:36 ` [PATCH 5/6] gdb/testsuite: fix gdb.debuginfod/fetch_src_and_symbols.exp with Clang Andrew Burgess
2022-11-16 16:29 ` Tom Tromey
2022-11-17 11:38 ` [PATCHv2 0/2] Fix " Andrew Burgess
2022-11-17 11:38 ` Andrew Burgess [this message]
2022-11-17 11:38 ` [PATCHv2 2/2] gdb/testsuite: fix " Andrew Burgess
2022-11-17 19:29 ` [PATCHv2 0/2] Fix " Tom Tromey
2022-11-11 16:36 ` [PATCH 6/6] gdb/testsuite: rewrite gdb.cp/call-method-register.exp with dwarf assembler Andrew Burgess
2022-11-16 11:59 ` Lancelot SIX
2022-11-16 16:32 ` [PATCH 0/6] The DWARF assembler and Clang Tom Tromey
2022-11-18 11:48 ` Andrew Burgess
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=fd18571a140245d1151e824ac324a784dfb89b28.1668684812.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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: link
Be 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).