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:15:43 +0200	[thread overview]
Message-ID: <1440080143.3117.125.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 8737zefc75.fsf@smart-cactus.org

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

On Thu, 2015-08-20 at 13:09 +0200, Ben Gamari wrote:
> It turns out that libbacktrace only uses DWARF line information, not
> the .debug_frames unwinding information.

It might indeed be that libbacktrace only handles .eh_frame.
If you already generate .debug_frame it should be easy to
generate .eh_frame information. The formats are almost the same with a
few small encoding differences (also .eh_frame can have a .eh_frame_hdr
index which makes address lookup and unwinding much more efficient).
http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/ehframechpt.html
http://www.airs.com/blog/archives/460

Alternatively it might not be too hard to make libbacktrace
use .debug_frame if it is already loading the .debug_line info then
making it also load .debug_frame and interpret it mostly like .eh_frame
is. (elfutils libdw cie.c/fde.c use CFI_IS_EH to distinquish if you want
to see some of the practical differences)

Again, not wanting you to push away towards another library, but simply
pointing out different options.

Cheers,

Mark

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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 14:15 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:13 Ben Gamari
2015-08-20 14:04 Mark Wielaard
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=1440080143.3117.125.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).