summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.linespec
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2021-09-30 11:52:21 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2021-09-30 15:27:39 -0400
commit4dfef5be6812dd7abfbc8f18e9c0384f2522b511 (patch)
tree90aa986d915c17f2320655298e2799d3a2cd1841 /gdb/testsuite/gdb.linespec
parent2fed9db40b1179f62c6fb0f2cacfb0db6b50af46 (diff)
downloadbinutils-gdb-4dfef5be6812dd7abfbc8f18e9c0384f2522b511.tar.gz
gdb/testsuite: make runto_main not pass no-message to runto
As follow-up to this discussion: https://sourceware.org/pipermail/gdb-patches/2020-August/171385.html ... make runto_main not pass no-message to runto. This means that if we fail to run to main, for some reason, we'll emit a FAIL. This is the behavior we want the majority of (if not all) the time. Without this, we rely on tests logging a failure if runto_main fails, otherwise. They do so in a very inconsisteny mannet, sometimes using "fail", "unsupported" or "untested". The messages also vary widly. This patch removes all these messages as well. Also, remove a few "fail" where we call runto (and not runto_main). by default (without an explicit no-message argument), runto prints a failure already. In two places, gdb.multi/multi-re-run.exp and gdb.python/py-pp-registration.exp, remove "message" passed to runto. This removes a few PASSes that we don't care about (but FAILs will still be printed if we fail to run to where we want to). This aligns their behavior with the rest of the testsuite. Change-Id: Ib763c98c5f4fb6898886b635210d7c34bd4b9023
Diffstat (limited to 'gdb/testsuite/gdb.linespec')
-rw-r--r--gdb/testsuite/gdb.linespec/keywords.exp1
-rw-r--r--gdb/testsuite/gdb.linespec/ls-errs.exp1
-rw-r--r--gdb/testsuite/gdb.linespec/thread.exp1
3 files changed, 0 insertions, 3 deletions
diff --git a/gdb/testsuite/gdb.linespec/keywords.exp b/gdb/testsuite/gdb.linespec/keywords.exp
index b0ed18b42e0..88192690fc4 100644
--- a/gdb/testsuite/gdb.linespec/keywords.exp
+++ b/gdb/testsuite/gdb.linespec/keywords.exp
@@ -23,7 +23,6 @@ if {[prepare_for_testing "failed to prepare" $exefile $srcfile {debug}]} {
}
if ![runto_main] {
- fail "can't run to main"
return 0
}
diff --git a/gdb/testsuite/gdb.linespec/ls-errs.exp b/gdb/testsuite/gdb.linespec/ls-errs.exp
index 99b0f393bb8..10c5d32122c 100644
--- a/gdb/testsuite/gdb.linespec/ls-errs.exp
+++ b/gdb/testsuite/gdb.linespec/ls-errs.exp
@@ -48,7 +48,6 @@ proc do_test {lang} {
gdb_test_no_output "set max-completions unlimited"
if {![runto_main]} {
- fail "can't run to main"
return 0
}
diff --git a/gdb/testsuite/gdb.linespec/thread.exp b/gdb/testsuite/gdb.linespec/thread.exp
index 578a4da77cc..ab631a01647 100644
--- a/gdb/testsuite/gdb.linespec/thread.exp
+++ b/gdb/testsuite/gdb.linespec/thread.exp
@@ -24,7 +24,6 @@ if {[prepare_for_testing "failed to prepare" $exefile $srcfile {debug}]} {
}
if ![runto_main] {
- fail "can't run to main"
return 0
}