From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 2/3] [gdb/testsuite] Use have_gnu_debuglink in two more test-cases
Date: Tue, 20 Oct 2026 09:01:56 +0200 [thread overview]
Message-ID: <20261020070157.2414518-3-tdevries@suse.de> (raw)
In-Reply-To: <20261020070157.2414518-1-tdevries@suse.de>
When running test-cases gdb.debuginfod/crc_mismatch.exp and
gdb.debuginfod/solib-with-soname.exp with target board cc-with-gnu-debuglink,
we get:
...
UNSUPPORTED: gdb.debuginfod/crc_mismatch.exp: \
cannot produce separate debug info files
UNSUPPORTED: gdb.debuginfod/solib-with-soname.exp: \
debug information has been split to a separate file
...
Use proc have_gnu_debuglink to get the more precise:
...
UNSUPPORTED: gdb.debuginfod/crc_mismatch.exp: \
require failed: !have_gnu_debuglink $binfile
UNSUPPORTED: gdb.debuginfod/solib-with-soname.exp: \
require failed: !have_gnu_debuglink $binfile
...
---
gdb/testsuite/gdb.debuginfod/crc_mismatch.exp | 2 ++
gdb/testsuite/gdb.debuginfod/solib-with-soname.exp | 6 ++----
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/testsuite/gdb.debuginfod/crc_mismatch.exp b/gdb/testsuite/gdb.debuginfod/crc_mismatch.exp
index 35f91bff261..9bf65c4e0e6 100644
--- a/gdb/testsuite/gdb.debuginfod/crc_mismatch.exp
+++ b/gdb/testsuite/gdb.debuginfod/crc_mismatch.exp
@@ -31,6 +31,8 @@ if {[build_executable "build executable" $testfile $srcfile debug] == -1} {
return
}
+require {!have_gnu_debuglink $binfile}
+
# The procedure gdb_gnu_strip_debug will produce an executable called
# ${binfile}, which is just like the executable ($binfile) but without
# the debuginfo. Instead $binfile has a .gnu_debuglink section which
diff --git a/gdb/testsuite/gdb.debuginfod/solib-with-soname.exp b/gdb/testsuite/gdb.debuginfod/solib-with-soname.exp
index 12f0011d457..af6d548c37d 100644
--- a/gdb/testsuite/gdb.debuginfod/solib-with-soname.exp
+++ b/gdb/testsuite/gdb.debuginfod/solib-with-soname.exp
@@ -103,16 +103,14 @@ require {expect_build_id_in_core_file $binfile}
# If the board file is automatically splitting the debug information
# into a separate file (e.g. the cc-with-gnu-debuglink.exp board) then
# this test isn't going to work.
+require {!have_gnu_debuglink $binfile}
+
clean_restart
gdb_file_cmd $binfile
if {$gdb_file_cmd_debug_info ne "debug"} {
unsupported "failed to find debug information"
return
}
-if {[regexp "${testfile}.debug" $gdb_file_cmd_msg]} {
- unsupported "debug information has been split to a separate file"
- return
-}
# Run BINFILE which will generate a corefile.
set corefile [core_find $binfile]
--
2.51.0
next prev parent reply other threads:[~2026-10-20 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 7:01 [pushed 0/3] [gdb/testsuite] cc-with-gnu-debuglink fixes Tom de Vries
2026-10-20 7:01 ` [pushed 1/3] [gdb/testsuite] Factor out have_gnu_debuglink Tom de Vries
2026-10-20 7:01 ` Tom de Vries [this message]
2026-10-20 7:01 ` [pushed 3/3] [gdb/testsuite] Skip debuginfod tests with cc-with-gnu-debuglink board Tom de Vries
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=20261020070157.2414518-3-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