Re: [Libunwind-devel] Unwinding from optimzied shared library on linux

[Arun Sharma]

On Mon, Sep 22, 2014 at 10:34 PM, Scott Biersdorff
<address@hidden> wrote:
> Hi Arun,
>
> There are many more entries like this one in the library, here is another one:
>
> 00016430 0000000000000014 0000000000016434 FDE cie=00000000 
> pc=00000000002aa500..00000000002aa5b1
>    LOC           CFA      ra
> 00000000002aa500 rsp+8    c-8
> 00000000002aa504 rsp+48   c-8
> 00000000002aa5b0 rsp+8    c-8
>
> This one might be of particular interest since the first location libunwind 
> recovered (00000000002aa500), is in this address range.

It's also interesting that the IP is exactly the first byte of this
range. We need to figure out if we got to that location using the
normal call/ret sequence or an async event (such as signal).

Please see the comment in

src/dwarf/Gparser.c:fetch_proc_info() around use_prev_instr

I suspect there have been bug fixes in this area since the 1.1
release. Is it possible for you to test git head?

 -Arun