public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/23504] index cache: Produce and consume DWARF5 format
Date: Sun, 21 Feb 2021 22:48:18 +0000 [thread overview]
Message-ID: <bug-23504-4717-LUkyUti4K9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23504-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23504
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom Tromey from comment #2)
> (In reply to Tom Tromey from comment #1)
>
> > Anyway, if that is fixed, then I think the separate .debug_str problem
> > will go away -- because, IIUC, the index will only refer to strings
> > that are already present in the existing string section.
>
> This is unfortunately mistaken. If the .debug_info uses an inline
> string, then it won't appear in .debug_str.
I might be missing some context why the string representation is important. But
if it is, then note that besides DW_FORM_strp, DW_FORM_string and
DW_FORM_strx[1234] (which will indirectly end up in .debug_str), there is also
DW_FORM_line_strp (which points to .debug_line_str) which is used for file/path
related strings (gcc 11 for example will make sure that the CU DIE name and
compdir end up there).
And of course there is DW_FORM_strp_sup and DW_FORM_GNU_strp_alt for shared
strings in the multi/sup file .debug_str.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-21 22:48 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 [this message]
2021-02-22 2:27 ` tromey at sourceware dot org
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-LUkyUti4K9@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: link
Be 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).