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 gdb/23504] index cache: Produce and consume DWARF5 format Date: Mon, 22 Feb 2021 02:27:03 +0000 [thread overview] Message-ID: <bug-23504-4717-e9GfbwVqlV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-23504-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=23504 --- Comment #4 from Tom Tromey <tromey at sourceware dot org> --- The context here is GDB generating an index and putting it into the index cache. .debug_names refers to symbol names using their index in .debug_str, so if a string does not appear there, then how would GDB cope? Currently I think it writes out a new .debug_str section, but of course (see the other PR), what's currently done is wrong; and also this seemed weird for the index cache, because in that scenario nobody is rewriting the original object file. Not sure if this is clear or not... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-22 2:27 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23504-4717@http.sourceware.org/bugzilla/> 2020-11-12 15:49 ` tromey at sourceware dot org 2021-02-21 22:33 ` tromey at sourceware dot org 2021-02-21 22:48 ` mark at klomp dot org 2021-02-22 2:27 ` tromey at sourceware dot org [this message] 2021-02-22 2:36 ` tromey at sourceware dot org 2021-02-24 14:22 ` mark at klomp dot org 2021-03-28 16:15 ` tromey at sourceware dot org 2021-03-28 19:41 ` tromey at sourceware dot org 2021-03-29 15:51 ` tromey at sourceware dot org 2022-04-22 18:36 ` tromey at sourceware dot org 2022-09-20 22:41 ` tromey at sourceware dot org 2023-12-10 15:17 ` tromey at sourceware dot org 2023-12-10 15:31 ` tromey at sourceware dot org 2023-12-10 15:51 ` tromey at sourceware dot org 2024-01-18 20:38 ` tromey at sourceware dot org 2024-02-09 20:04 ` tromey at sourceware 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-23504-4717-e9GfbwVqlV@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).