y 24, 2016 at 10:07 AM, Jakub Jelinek wrote:
> On Tue, May 24, 2016 at 09:46:58AM +0200, Francesco Zappa Nardelli wrote:
> > Dear David and all
> >
> > If you could produce a small object file..
> >
> >
> > Invoking readelf on /lib/x86_64-linux-gnu/libc.s
CIE bytecode.
Wonder if I am missing something...
-francesco
On Tue, May 24, 2016 at 1:34 AM, David Anderson
wrote:
> On 05/23/2016 02:10 PM, Francesco Zappa Nardelli wrote:
> > Dear DWARF-discuss
> >
> > I am writing a parser of eh-frame informations and I have a doubt about
Dear DWARF-discuss
I am writing a parser of eh-frame informations and I have a doubt about a
behaviour of readelf.
On a (statically linked) binary readelf reports the following eh-frame CIE
entry:
6f38 0014 CIE
Version: 1
Augmentation: "zRS"
Cod
Dear all
> I am still confused though, can we check this example together?
Sorry for the noise, I made a silly mistake and the addresses in the
hexdump, which are off by 0x10. Problem solved, thank you for the help!
-francesco
> Here is an annotated hexdump for the first CIE and FDE of an eh_
Cary, thanks for your reply! I am still confused though, can we check this
example together?
Here is an annotated hexdump for the first CIE and FDE of an eh_frame table:
$ hexdump -C -s 0x580 -n 658 foo2
0580 14 00 00 00 00 00 00 00 01 7a 52 00 01 78 10 01
length| ID|
Dear all
I have a question about the FDE encoding in eh_frame (and not dwarf_frame)
tables.
This document (I could not find a better description of eh_frame)
http://www.airs.com/blog/archives/460
states that:
"An FDE starts with the length and ID described above, and then continues
as foll
