public inbox for
 help / color / mirror / Atom feed
From: "d.filder at web dot de" <>
Subject: [Bug default/27363] New: Emit more detailed diagnostic output for "Unknown DWARF"
Date: Sun, 07 Feb 2021 11:06:43 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 27363
           Summary: Emit more detailed diagnostic output for "Unknown
           Product: dwz
           Version: unspecified
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: d.filder at web dot de
                CC: dwz at sourceware dot org
  Target Milestone: ---

The terseness of the current "Unknown DWARF" error messages makes it
very difficult to analyze what is going on in cases of not yet
parseable or standard-violating DWARF data.  They should give more
information, namely include:

- a hexdump of the data around the offending entity,
- whether the entity is invalid (get_DW_*_name()==NULL) or merely not
  yet handled by the code,
- current values of DW_AT_{name,producer,comp_dir,language,...},
- and instructions to include that output in the bug report and retain
  a copy of the unstripped binary for upload upon request.

From my cursory understanding the 3rd item might be easily
implementable with global variables holding copies of the most
recently seen values.


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

             reply	other threads:[~2021-02-07 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 11:06 d.filder at web dot de [this message]
2021-02-21 16:38 ` [Bug default/27363] " mark at klomp dot org
2022-06-30 13:26 ` mark at klomp dot org

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).