From: "dblaikie at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/22288] eu-addr2line doesn't find a rust file:line
Date: Tue, 24 May 2022 00:18:14 +0000 [thread overview]
Message-ID: <bug-22288-10460-0eFsQ1EOXw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22288-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22288
--- Comment #5 from David Blaikie <dblaikie at gmail dot com> ---
Just a quick +1 to Comment #2 - consumers shouldn't rely on the presence of
.debug_aranges, or them being complete (DWARF doesn't require/guarantee this -
and Clang doesn't emit aranges by default, for instance). Each contribution to
.debug_aranges says which CU it covers and any CUs not covered should be
parsed/assumed to contain things covering other addresses.
Ideally parsing CUs lightly (just enough to get their CU ranges) should be
fairly cheap - cheap enough to be worth doing so to avoid/save producers having
to emit all the extra/duplicate data into .debug_aranges that's already covered
by CU ranges.
It'd be nice if Rust could revert/avoid emitting these aranges, like Clang
does.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-05-24 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 18:56 [Bug tools/22288] New: " jistone at redhat dot com
2017-10-12 20:36 ` [Bug tools/22288] " mark at klomp dot org
2017-10-12 20:49 ` jistone at redhat dot com
2017-10-12 22:42 ` jistone at redhat dot com
2019-11-19 17:24 ` jistone at redhat dot com
2022-05-24 0:18 ` dblaikie at gmail dot com [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-22288-10460-0eFsQ1EOXw@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).