public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Sasha Da Rocha Pinheiro <darochapinhe@wisc.edu>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Dwarf_FDE (libdw)
Date: Fri, 21 Jul 2017 19:39:00 -0000	[thread overview]
Message-ID: <1500665962.14595.478.camel@klomp.org> (raw)
In-Reply-To: <BN6PR06MB30906C0218E8B06135F18B87A6A10@BN6PR06MB3090.namprd06.prod.outlook.com>

On Tue, 2017-07-18 at 16:50 +0000, Sasha Da Rocha Pinheiro wrote:
> From: Mark Wielaard <mark@klomp.org>
>> The thing is I need to get catch blocks, and eh_frame is not exactly
>> > Dwarf format. That's why I need FDE augmentation data also.
>> > Libdw doesn't do this, am I correct?
>> 
>> libdw handles both .debug_frame and .eh_frame data.
>> And you can use the Dwarf_Frames to unwind.
>> I believe the only thing not directly exposed are the lsda and
>> personality pointers. Is that the functionality that you need for
>> "catch blocks"?
>
> Are you thinking in exposing them?

I am thinking about it. But we don't currently store them. So we would
have reparse them. And since I haven't used them myself I am not sure
what they best way is to expose them. Are you currently using
Dwarf_Frames or Dwarf_CFI_Entry? Could you show some code that uses the
CFI with personality routines and lsda?

Thanks,

Mark

P.S. Please don't top-post. It makes it really hard to see the context.
P.P.S. Please don't add HTML to your postings. The mailinglist will drop
such messages.

      parent reply	other threads:[~2017-07-21 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15  1:01 Sasha Da Rocha Pinheiro
2017-07-15 21:30 ` Mark Wielaard
2017-07-17  4:13   ` Sasha Da Rocha Pinheiro
2017-07-17 13:29     ` Mark Wielaard
2017-07-17 17:16       ` Sasha Da Rocha Pinheiro
2017-07-17 17:48         ` Mark Wielaard
2017-07-17 17:53           ` Sasha Da Rocha Pinheiro
     [not found]           ` <BN6PR06MB30906C0218E8B06135F18B87A6A10@BN6PR06MB3090.namprd06.prod.outlook.com>
2017-07-21 19:39             ` Mark Wielaard [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=1500665962.14595.478.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=darochapinhe@wisc.edu \
    --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).