From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/21247] addr2line doesn't properly resolve filename/lineno
Date: Fri, 05 May 2017 16:47:00 -0000 [thread overview]
Message-ID: <bug-21247-10460-EpCuvIx3VV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21247-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21247
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
Looking at the debug_info we do have:
[39ca09] subprogram
low_pc (addr) +0x00000000002c08b0
<_Z20PlatformCrashHandleriP9siginfo_tPv>
high_pc (addr) +0x00000000002c0a05
lo_user+0x1fe7 (flag) Yes
frame_base (block1)
[ 0] reg7
MIPS_linkage_name (strp)
"_Z20PlatformCrashHandleriP9siginfo_tPv"
name (strp) "PlatformCrashHandler"
decl_file (data1) 107
decl_line (data2) 580
external (flag) Yes
lo_user+0x1fe1 (flag) Yes
Which is inside a compile_unit generated by clang:
[29d634] compile_unit
producer (strp) "clang version 3.7.1
(tags/RELEASE_371/fi
nal)"
language (data2) C_plus_plus (4)
name (strp) "-"
stmt_list (data4) 581678
comp_dir (strp)
"/home/marat/production/ue4/Engine/Source
"
lo_user+0x1fe1 (flag) Yes
low_pc (addr) +000000000000000000
ranges (data4) range list [ c92e0]
Note that the low_pc seems bogus (zero). And the range list seems bogus too (it
consists of 800+ entries some of which look bogus too
(+0x0000000000000001..+0x0000000000000001) and none seem to actually cover that
function addresses.
See also this discussion on the mailinglist:
https://sourceware.org/ml/elfutils-devel/2017-q2/msg00190.html
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-05-05 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 19:39 [Bug tools/21247] New: " marat at slonopotamus dot org
2017-03-13 20:06 ` [Bug tools/21247] " marat at slonopotamus dot org
2017-03-17 20:14 ` marat at slonopotamus dot org
2017-05-02 11:20 ` mark at klomp dot org
2017-05-05 16:47 ` 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-21247-10460-EpCuvIx3VV@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).