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 0/3] [gdb/testsuite] cc-with-gnu-debuglink fixes
Date: Tue, 20 Oct 2026 09:01:54 +0200	[thread overview]
Message-ID: <20261020070157.2414518-1-tdevries@suse.de> (raw)

This series contains three patches that improve handling of the
cc-with-gnu-debuglink target board.

Tested on x86_64-linux.

Tom de Vries (3):
  [gdb/testsuite] Factor out have_gnu_debuglink
  [gdb/testsuite] Use have_gnu_debuglink in two more test-cases
  [gdb/testsuite] Skip debuginfod tests with cc-with-gnu-debuglink board

 gdb/testsuite/gdb.base/dwz-symtabs.exp                     | 5 +----
 gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp | 2 ++
 gdb/testsuite/gdb.debuginfod/crc_mismatch.exp              | 2 ++
 gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp     | 2 ++
 gdb/testsuite/gdb.debuginfod/solib-with-dwz.exp            | 5 +----
 gdb/testsuite/gdb.debuginfod/solib-with-soname.exp         | 6 ++----
 .../gdb.dwarf2/sig-type-unnamed-class-bad-sig.exp          | 2 +-
 gdb/testsuite/gdb.tui/activate-from-secondary-prompt.exp   | 7 ++-----
 gdb/testsuite/gdb.tui/debuginfod-query.exp                 | 5 +----
 gdb/testsuite/lib/gdb.exp                                  | 5 +++++
 10 files changed, 19 insertions(+), 22 deletions(-)


base-commit: b89169e9d457c0e7ec8f88b7dfd102ca657a6e83
-- 
2.51.0


             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 Tom de Vries [this message]
2026-10-20  7:01 ` [pushed 1/3] [gdb/testsuite] Factor out have_gnu_debuglink Tom de Vries
2026-10-20  7:01 ` [pushed 2/3] [gdb/testsuite] Use have_gnu_debuglink in two more test-cases Tom de Vries
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-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