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: Tue, 02 May 2017 11:20:00 -0000 [thread overview]
Message-ID: <bug-21247-10460-mv3WT5n7ZC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21247-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21247
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
Dumping the whole decoded line table with eu-readelf --debug-dump=decodedline
shows:
/home/marat/production/ue4/Engine/Source/Runtime/Core/Private/Linux/LinuxPlatformCrashContext.cpp
(mtime: 0, length: 0)
593:6 S 0 0 0 +0x00000000002c099f
<_Z20PlatformCrashHandleriP9siginfo_tPv+0xef>
593:6 0 0 0 +0x00000000002c09ae
<_Z20PlatformCrashHandleriP9siginfo_tPv+0xfe>
595:3 S 0 0 0 +0x00000000002c09b0
<_Z20PlatformCrashHandleriP9siginfo_tPv+0x100>
600:3 S 0 0 0 +0x00000000002c09b4
<_Z20PlatformCrashHandleriP9siginfo_tPv+0x104>
75:1 S 0 0 0 +0x00000000002c09b9
<_Z20PlatformCrashHandleriP9siginfo_tPv+0x109>
76:6 S 0 0 0 +0x00000000002c09be
<_Z20PlatformCrashHandleriP9siginfo_tPv+0x10e>
So there we are able to also deduce that address 0x2c09b2 is associated with
LinuxPlatformCrashContext.cpp:595:3
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-05-01 14:40 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 [this message]
2017-05-05 16:47 ` 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:
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-mv3WT5n7ZC@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).