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: [PATCH 0/3] [gdb/testsuite] Fix some dwarf assembly test-cases
Date: Wed, 20 May 2026 17:38:29 +0200	[thread overview]
Message-ID: <20260520153832.3600888-1-tdevries@suse.de> (raw)

I ran readelf -w on the executable from test-case
gdb.dwarf2/imported-unit-c.exp, and saw some warnings.

This patch series fixes those, and a few more warnings in other test-cases
that I found using readelf -w and llvm-dwarfdump -a.

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

Tom de Vries (3):
  [gdb/testsuite] Clean up gdb.dwarf2/imported-unit-c.exp
  [gdb/testsuite] Clean up duplicate .debug_aranges terminators
  [gdb/testsuite] Don't generate dummy CUs in dwz files

 gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl       |  4 +-
 gdb/testsuite/gdb.dwarf2/imported-unit-c.exp  | 40 -------------------
 gdb/testsuite/gdb.dwarf2/short-build-id.exp   |  1 -
 .../gdb.dwarf2/struct-with-sig-2.exp          |  2 +-
 4 files changed, 2 insertions(+), 45 deletions(-)


base-commit: 8822682db0b86fcbf16b41397424cd78d48c924d
-- 
2.51.0


             reply	other threads:[~2026-05-20 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 15:38 Tom de Vries [this message]
2026-05-20 15:38 ` [PATCH 1/3] [gdb/testsuite] Clean up gdb.dwarf2/imported-unit-c.exp Tom de Vries
2026-05-20 15:38 ` [PATCH 2/3] [gdb/testsuite] Clean up duplicate .debug_aranges terminators Tom de Vries
2026-05-20 15:38 ` [PATCH 3/3] [gdb/testsuite] Don't generate dummy CUs in dwz files Tom de Vries
2026-05-21 14:07 ` [PATCH 0/3] [gdb/testsuite] Fix some dwarf assembly test-cases Tom Tromey

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=20260520153832.3600888-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