public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/31132] New: .debug_names writer should create .debug_aranges Date: Sun, 10 Dec 2023 15:30:42 +0000 [thread overview] Message-ID: <bug-31132-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31132 Bug ID: 31132 Summary: .debug_names writer should create .debug_aranges Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- Currently gdb can write .debug_names but it will not create .debug_aranges. However, when reading, if .debug_aranges does not exist, then gdb will not use the index. This leads to the funny situation that gdb will create an index that it will not use. Also, this is a barrier to changing the index cache to use .debug_names. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-12-10 15:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-10 15:30 tromey at sourceware dot org [this message] 2023-12-10 15:30 ` [Bug symtab/31132] " tromey at sourceware dot org 2023-12-10 15:31 ` tromey at sourceware dot org 2023-12-10 20:57 ` tromey at sourceware dot org 2024-01-18 20:38 ` tromey at sourceware dot org 2025-01-05 19:01 ` mark at klomp dot org 2025-01-05 23:39 ` sam at gentoo dot org 2025-01-05 23:39 ` sam at gentoo dot 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-31132-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).