Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Check using_fission in allow_debuginfod_tests
Date: Tue, 20 Oct 2026 09:58:09 +0200	[thread overview]
Message-ID: <20261020075809.2426580-1-tdevries@suse.de> (raw)

With test-case gdb.debuginfod/fetch_src_and_symbols.exp and target board
dwarf5-fission-debug-types I run into:
...
(gdb) list 27
warning: 22     tmp-fetch_src_and_symbols.c: No such file or directory
(gdb) FAIL: $exp: local_url: list 27
...

The problem is that the test-case expects to start from a point where the
executable contains all the debug info, and when using fission that's not
the case.

We'd like to test fission in combination with debuginfod, but currently that's
not supported by debuginfod [1].

Fix this by skipping debuginfod test-cases when using fission.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34751

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=32184
---
 gdb/testsuite/lib/debuginfod-support.exp | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/gdb/testsuite/lib/debuginfod-support.exp b/gdb/testsuite/lib/debuginfod-support.exp
index 66b4098d4f9..1d11c5bea8b 100644
--- a/gdb/testsuite/lib/debuginfod-support.exp
+++ b/gdb/testsuite/lib/debuginfod-support.exp
@@ -33,6 +33,22 @@ proc allow_debuginfod_tests {} {
 	return false
     }
 
+    if {[using_fission]} {
+	# Debuginfod test-cases tend to split off debuginfo and move it to a
+	# place where gdb can't find it, but debuginfod can.
+	#
+	# Fission is another way to split off debuginfo, in the sense that only
+	# the skeleton units stay in the executable.  We'd like to test that
+	# debuginfod can serve .dwo or .dwp files, but that's currently not
+	# supported (PR debuginfod/32184).
+	#
+	# Return false because most debuginfod test-cases assume one
+	# particular type of split-off debuginfo.  There are a few that don't,
+	# but allowing those to run with fission doesn't actually test the
+	# fission+debuginfod behavior that we want to test.
+	return false
+    }
+
     # Skip testing if gdb was not configured with debuginfod.
     #
     # If GDB is built with ASan, it warns that some signal handlers

base-commit: 60e638ccd7de0776e72cae0cdcf7cc79b658cc95
-- 
2.51.0


                 reply	other threads:[~2026-10-20  7:58 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=20261020075809.2426580-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