public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libdw: Handle split Dwarf Dies in dwarf_die_addr_die.
Date: Thu, 31 May 2018 15:06:00 -0000	[thread overview]
Message-ID: <1527779194.12946.30.camel@klomp.org> (raw)
In-Reply-To: <1527631870.12946.9.camel@klomp.org>

On Wed, 2018-05-30 at 00:11 +0200, Mark Wielaard wrote:
> On Tue, 2018-05-29 at 23:57 +0200, Mark Wielaard wrote:
> > dwarf_die_addr_die can be used to turn an Dwarf_Die addr back into a
> > full Dwarf_Die, just given the original Dwarf debug handle. This now
> > also works for Dwarf_Dies which originated from a split Dwarf. Whenever
> > a split Dwarf_CU is found the Dwarf it originated from is registered
> > with the Dwarf that the skeleton Dwarf_CU came from. All registered
> > split Dwarfs are then searched by dwarf_die_addr_die if the addr didn't
> > match the main Dwarf or the alt Dwarf.
> > 
> > One limitation in this implementation is that only DIEs that come from
> > the main .debug_info in the .dwo are supported. Theoretically there could
> > also be DIEs in an .debug_type or from other/multiple (comdat) sections.
> > 
> > New tests are added for dwarf-4, dwarf-5, split-dwarf-4, split-dwarf-5
> > and version 4 and 5 dwo files.
> 
> And clearly I hadn't done a make distcheck because then I would have
> known that valgrind would warn about leaking the new search tree.

Pushed to master, including the tdestoy fix for the leak.

      reply	other threads:[~2018-05-31 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 21:57 Mark Wielaard
2018-05-29 22:11 ` Mark Wielaard
2018-05-31 15:06   ` 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=1527779194.12946.30.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).