public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Using dwfl to enumerate frames of current thread
Date: Thu, 20 Aug 2015 16:04:19 +0200	[thread overview]
Message-ID: <1440079459.3117.117.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 87y4h6dt36.fsf@smart-cactus.org

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On Thu, 2015-08-20 at 14:47 +0200, Ben Gamari wrote:
> Using elfutils 0.163, built by me with all dependencies available,
> 
>     $ /opt/exp/elfutils-root/bin/addr2line --version
>     addr2line (elfutils) 0.163
>     Copyright (C) 2012 Red Hat, Inc.
>     This is free software; see the source for copying conditions.  There is NO
>     warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>     Written by Ulrich Drepper.
> 
>     $ /opt/exp/elfutils-root/bin/addr2line -e inplace/lib/bin/ghc-stage2 -f 0x25a6898
>     base_TextziParserCombinatorsziReadP_zdfAlternativePzuzdczlzbzg_info
>     ??:0
> 
> What am I doing wrong here?

Probably just a bug/missing feature in elfutils. If the binary is
statically linked it might be that we are not able to find all
information we need. There have been other reports about that.
https://bugzilla.redhat.com/show_bug.cgi?id=1053583
Given that most binaries are not static it hasn't been a problem in
practice.

Could you post the binary somewhere?
Then I will take a look at what is going wrong.

Thanks,

Mark

             reply	other threads:[~2015-08-20 14:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 14:04 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-25 12:23 Mark Wielaard
2015-08-25 10:59 Ben Gamari
2015-08-23 21:57 Mark Wielaard
2015-08-22 10:18 Ben Gamari
2015-08-21 22:53 Mark Wielaard
2015-08-21 22:41 Mark Wielaard
2015-08-21 16:25 Ben Gamari
2015-08-21 14:41 Ben Gamari
2015-08-21 14:26 Mark Wielaard
2015-08-21  7:35 Ben Gamari
2015-08-20 17:39 Mark Wielaard
2015-08-20 17:32 Mark Wielaard
2015-08-20 17:06 Josh Stone
2015-08-20 15:32 Mark Wielaard
2015-08-20 15:02 Ben Gamari
2015-08-20 14:46 Mark Wielaard
2015-08-20 14:28 Ben Gamari
2015-08-20 14:15 Mark Wielaard
2015-08-20 14:13 Ben Gamari
2015-08-20 12:47 Ben Gamari
2015-08-20 11:09 Ben Gamari
2015-08-19 14:25 Ben Gamari
2015-08-19 13:10 Mark Wielaard
2015-08-19 12:11 Ben Gamari

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=1440079459.3117.117.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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).