From: Mark Wielaard <mark@klomp.org>
To: dwz@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH 1/4] Recognize some new DWARF5 .debug sections.
Date: Mon, 14 Sep 2020 12:23:52 +0200 [thread overview]
Message-ID: <20200914102355.8137-2-mark@klomp.org> (raw)
In-Reply-To: <20200914102355.8137-1-mark@klomp.org>
Recognize .debug_loclists, .debug_rnglists, .debug_line_str. loclists,
rnglists and line_str cannot be moved into a supplemental file.
We already handle .debug_macro (the replacement for .debug_macinfo).
.debug_pubnames and .debug_pubtypes are no more, but we deleted them
already when found. There is a standardized variant of .gdb_index,
.debug_names, but gdb works fine with .gdb_index even for DWARF5, so
just keep supporting .gdb_index for now.
There are two new sections .debug_addr and .debug_str_offsets which
are only emitted in split-dwarf mode by GCC. For now we don't recognize
those because we don't handle split-dwarf.
Finally there is .debug_sup which is the standardized variant of
.gnu_debugaltlink. Which we should generate when operating in "full"
DWARF5 mode. But that would require changes to some consumers.
* dwz.c (enum debug_section_kind): Add DEBUG_LOCLISTS,
DEBUG_RNGLISTS and DEBUG_LINE_STR.
(debug_sections): Add .debug_loclists, .debug_rnglists and
.debug_line_str.
---
dwz.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/dwz.c b/dwz.c
index 7ec0623..6a4c96c 100644
--- a/dwz.c
+++ b/dwz.c
@@ -687,8 +687,11 @@ enum debug_section_kind
DEBUG_GNU_PUBTYPES,
DEBUG_MACINFO,
DEBUG_LOC,
+ DEBUG_LOCLISTS,
DEBUG_FRAME,
DEBUG_RANGES,
+ DEBUG_RNGLISTS,
+ DEBUG_LINE_STR,
DEBUG_GDB_SCRIPTS,
GDB_INDEX,
GNU_DEBUGALTLINK,
@@ -720,8 +723,11 @@ static struct
{ ".debug_gnu_pubtypes", NULL, NULL, 0, 0, 0 },
{ ".debug_macinfo", NULL, NULL, 0, 0, 0 },
{ ".debug_loc", NULL, NULL, 0, 0, 0 },
+ { ".debug_loclists", NULL, NULL, 0, 0, 0 },
{ ".debug_frame", NULL, NULL, 0, 0, 0 },
{ ".debug_ranges", NULL, NULL, 0, 0, 0 },
+ { ".debug_rnglists", NULL, NULL, 0, 0, 0 },
+ { ".debug_line_str", NULL, NULL, 0, 0, 0 },
{ ".debug_gdb_scripts", NULL, NULL, 0, 0, 0 },
{ ".gdb_index", NULL, NULL, 0, 0, 0 },
{ ".gnu_debugaltlink", NULL, NULL, 0, 0, 0 },
--
2.18.4
next prev parent reply other threads:[~2020-09-14 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 10:23 DWARF5 support for dwz Mark Wielaard
2020-09-14 10:23 ` Mark Wielaard [this message]
2020-09-14 10:36 ` [PATCH 1/4] Recognize some new DWARF5 .debug sections Jakub Jelinek
2020-09-14 10:23 ` [PATCH 2/4] Handle DWARF5 headers for compile and partial units Mark Wielaard
2020-09-14 10:38 ` Jakub Jelinek
2020-09-15 11:38 ` Mark Wielaard
2020-09-14 10:23 ` [PATCH 3/4] Handle new DWARF5 attributes Mark Wielaard
2020-09-14 10:38 ` Jakub Jelinek
2020-09-14 10:23 ` [PATCH 4/4] Handle new DWARF5 operations as their GNU extension variants Mark Wielaard
2020-09-14 10:39 ` Jakub Jelinek
2020-09-14 10:48 ` DWARF5 support for dwz Jakub Jelinek
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=20200914102355.8137-2-mark@klomp.org \
--to=mark@klomp.org \
--cc=dwz@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).