From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH][gdb/testsuite] Fix .debug_aranges in gdb.dwarf2/fission-loclists.S
Date: Tue, 2 Aug 2022 06:45:56 +0200 [thread overview]
Message-ID: <20220802044554.GA23254@delia.home> (raw)
Hi,
When running test-case gdb.dwarf2/fission-loclists.exp, I noticed:
...
warning: Section .debug_aranges in fission-loclists has duplicate \
debug_info_offset 0x8f, ignoring .debug_aranges.^M
...
Fix this by removing the duplicate .debug_aranges entry.
Tested on x86_64-linux.
Any comments?
Thanks,
- Tom
[gdb/testsuite] Fix .debug_aranges in gdb.dwarf2/fission-loclists.S
---
gdb/testsuite/gdb.dwarf2/fission-loclists.S | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/gdb/testsuite/gdb.dwarf2/fission-loclists.S b/gdb/testsuite/gdb.dwarf2/fission-loclists.S
index 012b2d7ac7d..cf12ab3b04c 100644
--- a/gdb/testsuite/gdb.dwarf2/fission-loclists.S
+++ b/gdb/testsuite/gdb.dwarf2/fission-loclists.S
@@ -523,20 +523,6 @@ main:
.quad .LFE1-.LFB1 # Length
.quad 0
.quad 0
- .section .debug_aranges,"",@progbits
- .4byte 0x3c # Length of Address Ranges Info
- .value 0x2 # DWARF Version
- .4byte .Lskeleton_debug_info0 # Offset of Compilation Unit Info
- .byte 0x8 # Size of Address
- .byte 0 # Size of Segment Descriptor
- .value 0 # Pad to 16 byte boundary
- .value 0
- .8byte .Ltext0 # Address
- .8byte .Letext0-.Ltext0 # Length
- .8byte .LFB1 # Address
- .8byte .LFE1-.LFB1 # Length
- .8byte 0
- .8byte 0
.section .debug_ranges,"",@progbits
.Ldebug_ranges0:
.8byte .Ltext0 - .Ltext0 # Offset 0
next reply other threads:[~2022-08-02 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 4:45 Tom de Vries via Gdb-patches [this message]
2022-08-04 17:52 ` 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=20220802044554.GA23254@delia.home \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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