From: Sasha Da Rocha Pinheiro <darochapinhe@wisc.edu>
To: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Dwarf_FDE (libdw)
Date: Sat, 15 Jul 2017 01:01:00 -0000 [thread overview]
Message-ID: <DM2PR06MB272B27552ECAA2BD3E967BCA6A20@DM2PR06MB272.namprd06.prod.outlook.com> (raw)
Hi,
I did not understand how to get the augmentation_data of a FDE. Could anyone explain me?
Also, is the start and end of Dwarf_FDE to be used as [initial_location, initial_location+address_range)??
Regards,
Sasha
typedef struct
{
/* Section offset of CIE this FDE refers to. This will never be
DW_CIE_ID_64 in an FDE. If this value is DW_CIE_ID_64, this is
actually a Dwarf_CIE structure. */
Dwarf_Off CIE_pointer;
/* We can't really decode anything further without looking up the CIE
and checking its augmentation string. Here follows the encoded
initial_location and address_range, then any augmentation data,
then the instruction stream. This FDE describes PC locations in
the byte range [initial_location, initial_location+address_range).
When the CIE augmentation string uses 'z', the augmentation data is
a DW_FORM_block (self-sized). Otherwise, when we understand the
augmentation string completely, fde_augmentation_data_size gives
the number of bytes of augmentation data before the instructions. */
const uint8_t *start;
const uint8_t *end;
} Dwarf_FDE;
next reply other threads:[~2017-07-15 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 1:01 Sasha Da Rocha Pinheiro [this message]
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
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=DM2PR06MB272B27552ECAA2BD3E967BCA6A20@DM2PR06MB272.namprd06.prod.outlook.com \
--to=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).