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/29385] New: [gdb, debug-types, debug-names, dwarf-5] Support .debug_names section with TUs in .debug_info Date: Tue, 19 Jul 2022 11:32:23 +0000 [thread overview] Message-ID: <bug-29385-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29385 Bug ID: 29385 Summary: [gdb, debug-types, debug-names, dwarf-5] Support .debug_names section with TUs in .debug_info Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- [ spin-off of PR29381. ] When running the test-case gdb.cp/cpexprs-debug-types.exp with target board cc-with-debug-names on a system which defaults to dwarf5, gdb rejects the .debug_names index because it cannot find a .debug_types section: ... The .debug_names index is rejected in dwarf2_read_debug_names because: ... if (map->tu_count != 0) { /* We can only handle a single .debug_types when we have an index. */ if (per_bfd->types.size () != 1) return false; ... The .debug_types section was eliminated in dwarf 5. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-19 11:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-19 11:32 vries at gcc dot gnu.org [this message] 2022-07-19 11:34 ` [Bug symtab/29385] " vries at gcc dot gnu.org 2022-08-12 14:22 ` vries at gcc dot gnu.org 2022-08-12 14:24 ` vries at gcc dot gnu.org 2022-08-12 15:49 ` vries at gcc dot gnu.org 2022-09-06 8:23 ` vries at gcc dot gnu.org 2022-09-06 8:23 ` 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-29385-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).