public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28573] New: Provide an dwarf_begin interface to open (single-file) DWO or GNU_LTO Dwarf subset
Date: Tue, 09 Nov 2021 18:13:41 +0000	[thread overview]
Message-ID: <bug-28573-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28573

            Bug ID: 28573
           Summary: Provide an dwarf_begin interface to open (single-file)
                    DWO or GNU_LTO Dwarf subset
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libdw
          Assignee: unassigned at sourceware dot org
          Reporter: mark at klomp dot org
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

To fix https://sourceware.org/bugzilla/show_bug.cgi?id=27367 "invalid loclists
data with -ffat-lto-objects" dwarf_begin_elf now checks to see which DWARF
subset is in the debug ELF file. And it picks the "plain" (.debug sections)
over "dwo" (.debug_...dwo sections) over "lto" (.gnu.debuglto_.debug sections)
in case multiple are in the same file. We have to pick one because mixing the
sections causes chaos.

But the user might want to pick a different set. In particular the user might
want to pick "single file" DWO (where the .dwo sections are in the same file as
the skeleton plain debug sections).

So we want to have a dwarf_begin variant with a flag to pick such a subset.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2021-11-09 18:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-28573-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.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).