public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27363] Emit more detailed diagnostic output for "Unknown DWARF"
Date: Thu, 30 Jun 2022 13:26:20 +0000	[thread overview]
Message-ID: <bug-27363-11298-9r78K9JJEM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27363-11298@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
For some reason I added commit 2 from comment #1 but not commit 1.
I have done so now:

commit beca0b4f1423f97f7a2da74a45f9f86d401e4ad2
Author: Mark Wielaard <mark@klomp.org>
Date:   Sun Feb 21 16:55:17 2021 +0100

    Print abbrev or DIE offset for Unknown DWARF error message.

            * dwz.c (read_abbrev): Add .debug_abbrev offset to error message.
            (read_exprloc): Print DIE offset that referenced the unknown
            operand in error message.
            (read_expr_low_mem_phase1): Likewise.
            (read_debug_info): Add die_offset to error messages for unknown
            forms, attributes extending beyond end of CU or unknown block
            form attributes.

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

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

      parent reply	other threads:[~2022-06-30 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 11:06 [Bug default/27363] New: " d.filder at web dot de
2021-02-21 16:38 ` [Bug default/27363] " mark at klomp dot org
2022-06-30 13:26 ` mark at klomp dot org [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=bug-27363-11298-9r78K9JJEM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.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).