From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Drop nosharedlibrary in some test-cases
Date: Fri, 18 Sep 2026 08:52:59 +0200 [thread overview]
Message-ID: <20260918065259.2754401-1-tdevries@suse.de> (raw)
After commit f35e32225f2 ("[gdb/testsuite] Speed up gdb.python/py-rbreak.exp")
which removed a superfluous runto_main/nosharedlibrary pair, I searched for
other cases where the same can be done.
Remove a few more superfluous runto_main/nosharedlibrary pairs.
Tested on x86_64-linux.
---
gdb/testsuite/gdb.base/info-types.exp.tcl | 6 ------
gdb/testsuite/gdb.fortran/info-modules.exp | 8 --------
gdb/testsuite/gdb.mi/mi-fortran-modules.exp | 5 -----
3 files changed, 19 deletions(-)
diff --git a/gdb/testsuite/gdb.base/info-types.exp.tcl b/gdb/testsuite/gdb.base/info-types.exp.tcl
index 057ca2fd1ee..19822b50843 100644
--- a/gdb/testsuite/gdb.base/info-types.exp.tcl
+++ b/gdb/testsuite/gdb.base/info-types.exp.tcl
@@ -33,12 +33,6 @@ proc run_test { lang } {
return -1
}
- if { ![runto_main] } {
- return 0
- }
-
- gdb_test_no_output "nosharedlibrary"
-
set file_re "File .*[string_to_regexp $srcfile]:"
if { $lang == "c++" } {
diff --git a/gdb/testsuite/gdb.fortran/info-modules.exp b/gdb/testsuite/gdb.fortran/info-modules.exp
index a1873900910..f94df7f1655 100644
--- a/gdb/testsuite/gdb.fortran/info-modules.exp
+++ b/gdb/testsuite/gdb.fortran/info-modules.exp
@@ -28,14 +28,6 @@ if { [prepare_for_testing "failed to prepare" $testfile \
return
}
-if { ![fortran_runto_main] } {
- perror "Could not run to main."
- return
-}
-
-# Avoid libc symbols.
-gdb_test "nosharedlibrary"
-
set logical4 [fortran_logical4]
set integer4 [fortran_int4]
set real4 [fortran_real4]
diff --git a/gdb/testsuite/gdb.mi/mi-fortran-modules.exp b/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
index c08d5c2038a..51e810c9271 100644
--- a/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
+++ b/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
@@ -30,11 +30,6 @@ if {[build_executable "failed to prepare" ${testfile} \
mi_clean_restart $::testfile
-mi_runto_main
-
-# Avoid libc symbols.
-mi_gdb_test {-interpreter-exec console "nosharedlibrary"}
-
# Patterns to skip optional system modules that appear with later versions of GFortran.
set system_modules_pattern \
"\{filename=\"\[^\"\]+/ieee/\[^/\]+\.F90\",fullname=\"\[^\"\]+\",symbols=\\\[(\[^\]\]+)\\\]\},.*"
base-commit: 0595410d007e5f628e14717cd268e557e166675f
--
2.51.0
reply other threads:[~2026-09-18 6:53 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=20260918065259.2754401-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@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: 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