public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org
Subject: Re: [PATCH] Add DIE offsets in error messages to make it easier to find what is wrong.
Date: Tue, 26 Jan 2021 21:49:22 +0100	[thread overview]
Message-ID: <20210126204922.GI4020736@tucnak> (raw)
In-Reply-To: <20210126204509.24710-1-mark@klomp.org>

On Tue, Jan 26, 2021 at 09:45:09PM +0100, Mark Wielaard wrote:
> With the following patch dwz will give a message like:
> 
> libmozjs-78.so: Couldn't find DIE at [bd6b507] referenced by
>   DW_AT_abstract_origin from DIE at [bd5bb9b]
> 
> Which makes it a easier to figure out what is going on.
> 
> In the above case it is easy to find the producer of the CU of those
> two DIEs. Which turned out the be is clang LLVM (rustc version 1.49.0)
> which seems to have gotten the abstract origin reference wrong.

LGTM, thanks.

	Jakub


      reply	other threads:[~2021-01-26 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 20:45 Mark Wielaard
2021-01-26 20:49 ` Jakub Jelinek [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=20210126204922.GI4020736@tucnak \
    --to=jakub@redhat.com \
    --cc=dwz@sourceware.org \
    --cc=mark@klomp.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).