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/25173] dwarf_getsrc_die fails for rust code
Date: Wed, 20 Nov 2019 13:18:00 -0000	[thread overview]
Message-ID: <bug-25173-10460-SZDYYzR1aR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25173-10460@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Milian Wolff from comment #7)
> hmm but in perfparser we have a workaround for missing aranges... I'll have
> to dig into this to see why it doesn't work here.

You also mention it is an issue with dwarf_getsrc_die in the subject. Which
would indicate that it is some other issue, because when you call
dwarf_getsrc_die you already would have found the DIE (by address). So maybe it
is something else in your case?

BTW. I do agree it would be nice if libdw handled missing debug_aranges. The
problem is simply that you cannot know the difference between missing and not
covered. Which means that for any address lookup that doesn't match an arange
you would have to do some fallback lookup, which could be expensive. So still
pondering how to handle this without penalizing debug files that do have
correct and complete aranges (maybe we could just handle the case where there
are just no  .debug_aranges at all, and only then make some fallback code kick
in?)

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

      parent reply	other threads:[~2019-11-20 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 19:25 [Bug libdw/25173] New: " mail at milianw dot de
2019-11-15 20:25 ` [Bug libdw/25173] " mark at klomp dot org
2019-11-16 20:09 ` mail at milianw dot de
2019-11-18 17:59 ` jistone at redhat dot com
2019-11-18 18:11 ` jistone at redhat dot com
2019-11-18 18:39 ` mark at klomp dot org
2019-11-18 18:47 ` jistone at redhat dot com
2019-11-20 13:12 ` mail at milianw dot de
2019-11-20 13:18 ` 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-25173-10460-SZDYYzR1aR@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).