aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.mi
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.mi
parent2fed9db40b1179f62c6fb0f2cacfb0db6b50af46 (diff)
downloadgdb-4dfef5be6812dd7abfbc8f18e9c0384f2522b511.zip
gdb-4dfef5be6812dd7abfbc8f18e9c0384f2522b511.tar.gz
gdb-4dfef5be6812dd7abfbc8f18e9c0384f2522b511.tar.bz2
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.mi')
-rw-r--r--gdb/testsuite/gdb.mi/mi-var-create-rtti.exp1
-rw-r--r--gdb/testsuite/gdb.mi/user-selected-context-sync.exp1
2 files changed, 0 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.mi/mi-var-create-rtti.exp b/gdb/testsuite/gdb.mi/mi-var-create-rtti.exp
index 095f436..d01f970 100644
--- a/gdb/testsuite/gdb.mi/mi-var-create-rtti.exp
+++ b/gdb/testsuite/gdb.mi/mi-var-create-rtti.exp
@@ -26,7 +26,6 @@ if [build_executable $testfile.exp $testfile $srcfile $opts] {
mi_clean_restart $binfile
if {[mi_runto_main] < 0} {
- untested "could not run to main"
return -1
}
diff --git a/gdb/testsuite/gdb.mi/user-selected-context-sync.exp b/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
index 2f1a488..df09da0 100644
--- a/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
+++ b/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
@@ -402,7 +402,6 @@ proc_with_prefix test_setup { mode } {
mi_gdb_load $binfile
if { [mi_runto_main] < 0 } {
- fail "can't run to main"
return
}