[PATCHv2 3/6] gdb/testsuite: move linespec test into gdb.linespec/ directory
Andrew Burgess
aburgess@redhat.com
Thu Jan 27 17:47:41 GMT 2022
The gdb.base/linespecs.exp test should really live in the gdb.linespec
directory, so lets move it there.
As we already have gdb.linespec/linespec.exp, I've renamed the test to
gdb.linespec/errors.exp, as this better reflects what the test is
actually checking.
Finally, the test script doesn't have its own source file, it was
reusing a random other source file, gdb.base/memattr.c. Now the tests
script is in gdb.linespec/, I've updated the test to use a different
source file from that directory.
---
.../{gdb.base/linespecs.exp => gdb.linespec/errors.exp} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename gdb/testsuite/{gdb.base/linespecs.exp => gdb.linespec/errors.exp} (94%)
diff --git a/gdb/testsuite/gdb.base/linespecs.exp b/gdb/testsuite/gdb.linespec/errors.exp
similarity index 94%
rename from gdb/testsuite/gdb.base/linespecs.exp
rename to gdb/testsuite/gdb.linespec/errors.exp
index bc16863a3e3..0baef1891a7 100644
--- a/gdb/testsuite/gdb.base/linespecs.exp
+++ b/gdb/testsuite/gdb.linespec/errors.exp
@@ -18,7 +18,7 @@
# We don't currently need our own test case for testing, so grab
# another one.
-if {[prepare_for_testing "failed to prepare" linespecs memattr.c]} {
+if {[prepare_for_testing "failed to prepare" linespecs keywords.c]} {
return -1
}
--
2.25.4
More information about the Gdb-patches
mailing list