public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix .debug_aranges in gdb.dwarf2/fission-loclists.S Date: Thu, 4 Aug 2022 17:56:11 +0000 (GMT) [thread overview] Message-ID: <20220804175611.123103856DE7@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=367dda85965bc03968edb43b2c86a2c25d3e846b commit 367dda85965bc03968edb43b2c86a2c25d3e846b Author: Tom de Vries <tdevries@suse.de> Date: Thu Aug 4 19:56:06 2022 +0200 [gdb/testsuite] Fix .debug_aranges in gdb.dwarf2/fission-loclists.S 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. Diff: --- 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
reply other threads:[~2022-08-04 17:56 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=20220804175611.123103856DE7@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).