From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/3] [gdb/testsuite] Clean up duplicate .debug_aranges terminators
Date: Wed, 20 May 2026 17:38:31 +0200 [thread overview]
Message-ID: <20260520153832.3600888-3-tdevries@suse.de> (raw)
In-Reply-To: <20260520153832.3600888-1-tdevries@suse.de>
I came across duplicate .debug_aranges terminators:
...
aranges {} cu_start {
arange {} 0 0
}
...
The dwarf assembler already generates a terminator, so there's no need to
generate another one.
Remove these.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34157
---
gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl | 2 --
gdb/testsuite/gdb.dwarf2/short-build-id.exp | 1 -
2 files changed, 3 deletions(-)
diff --git a/gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl b/gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl
index feb95f58feb..45a80bd7ce4 100644
--- a/gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl
+++ b/gdb/testsuite/gdb.dwarf2/dwzbuildid.tcl
@@ -57,7 +57,6 @@ proc write_just_debugaltlink {filename dwzname buildid} {
}
}
aranges {} cu_start {
- arange {} 0 0
}
}
}
@@ -97,7 +96,6 @@ proc write_dwarf_file {filename buildid {value 99}} {
}
aranges {} cu_start {
- arange {} 0 0
}
}
}
diff --git a/gdb/testsuite/gdb.dwarf2/short-build-id.exp b/gdb/testsuite/gdb.dwarf2/short-build-id.exp
index c30b82eb54f..d8a2f351f22 100644
--- a/gdb/testsuite/gdb.dwarf2/short-build-id.exp
+++ b/gdb/testsuite/gdb.dwarf2/short-build-id.exp
@@ -68,7 +68,6 @@ proc run_test { buildid } {
}
aranges {} cu_start {
- arange {} 0 0
}
}
--
2.51.0
next prev parent 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 [PATCH 0/3] [gdb/testsuite] Fix some dwarf assembly test-cases Tom de Vries
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 ` Tom de Vries [this message]
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-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