public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "marat at slonopotamus dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/21247] New: addr2line doesn't properly resolve filename/lineno
Date: Mon, 13 Mar 2017 19:39:00 -0000	[thread overview]
Message-ID: <bug-21247-10460@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 21247
           Summary: addr2line doesn't properly resolve filename/lineno
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tools
          Assignee: unassigned at sourceware dot org
          Reporter: marat at slonopotamus dot org
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Way to reproduce:

1. wget http://slonopotamus.org/libUE4Editor-Core.so (warning, 50MB)
2. ./src/addr2line -f -e libUE4Editor-Core.so 0x2c09b2

Expected output (as produced by addr2line from GNU binutils and I know that
this is correct):

_Z20PlatformCrashHandleriP9siginfo_tPv
/home/marat/production/ue4/Engine/Source/Runtime/Core/Private/Linux/LinuxPlatformCrashContext.cpp:595

Actual output (tested against commit e22cc80923f94e54c9384421904461958899db5b):

_Z20PlatformCrashHandleriP9siginfo_tPv
??:0

So, function name is resolved correctly but filename/lineno info is missing.

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

             reply	other threads:[~2017-03-13 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 19:39 marat at slonopotamus dot org [this message]
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

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@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).