Hi,

I'm trying to get libunwind working on 32-bit x86.  As far
as I can tell, it is never using the DWARF unwind info but instead
always falls back to following the frame-pointer chain.

Is this intended behaviour or am I doing something wrong?  (I am
compiling with -fasynchronous-unwind-tables).

Symptoms I'm seeing are:

1. if I unwind through a signal handler where the signal interrupted
either a function prologue or epilogue, then the back-trace is
incorrect.

2. unwinding with -fomit-frame-pointer doesn't work and often segfaults.

3. unw_proc_info_t.unwind_info member is always NULL.

Ralph.


_______________________________________________
Libunwind-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/libunwind-devel

Reply via email to