public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/25969] New: Ignoring .debug_aranges with clang .debug_names Date: Mon, 11 May 2020 09:10:16 +0000 [thread overview] Message-ID: <bug-25969-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25969 Bug ID: 25969 Summary: Ignoring .debug_aranges with clang .debug_names Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- [ Spinoff PR of PR25941 . ] Consider the patch and test-case submitted in https://sourceware.org/pipermail/gdb-patches/2020-May/168179.html . That is, test-case test.c: ... int main (void) { int sum,a,b; sum = a + b; return sum; } ... Compiled liked so: ... $ clang-10 test.c -gdwarf-5 -o test.out -gpubnames .. When loading into gdb, we have: ... $ gdb test.out warning: Section .debug_aranges in /data/gdb_versions/devel/test.out entry at offset 0 debug_info_offset 0 does not exists, ignoring .debug_aranges. ... The .debug_aranges warning triggers because the .debug_aranges section contains one entry: ... debug_aranges contents: Address Range Header: length = 0x0000002c, version = 0x0002, cu_offset = 0x00000000, addr_size = 0x08, seg_size = 0x00 [0x00000000004003c0, 0x00000000004003eb) ... which refers to the CU at offset 0, but the CU list (based on the CU list in .debug_names) only contains the one at 0xc7, so we fail to find it. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-05-11 9:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 9:10 vries at gcc dot gnu.org [this message] 2020-05-11 9:41 ` [Bug symtab/25969] " vries at gcc dot gnu.org 2020-09-22 6:18 ` sourav0311 at gmail dot com 2023-12-05 21:04 ` tromey at sourceware dot org 2023-12-06 9:29 ` cvs-commit at gcc dot gnu.org 2023-12-06 9:36 ` vries at gcc dot gnu.org
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=bug-25969-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).