From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] readelf: Handle .debug_info first if any other debug section needs it.
Date: Fri, 11 May 2018 15:37:00 -0000 [thread overview]
Message-ID: <1526053027.3097.62.camel@klomp.org> (raw)
In-Reply-To: <1525790979-2067-1-git-send-email-mark@klomp.org>
On Tue, 2018-05-08 at 16:49 +0200, Mark Wielaard wrote:
> Some debug sections need information from the CU DIEs to properly
> parse the data. Normally the .debug_info section is one of the first.
> But some DWARF producers reorder the sections and put it after some
> other debug sections. Make sure we first handle .debug_info if it
> is needed by any other debug section.
Pushed to master.
The observant reader noticed this patch also "handles" .dwo
files/sections, while the general support for that isn't in yet. I'll
post that patch soon. It is already present as WIP here:
https://code.wildebeest.org/git/user/mjw/elfutils/log/?h=dwarf5
Cheers,
Mark
prev parent reply other threads:[~2018-05-11 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 14:49 Mark Wielaard
2018-05-11 15:37 ` Mark Wielaard [this message]
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=1526053027.3097.62.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@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).