[libunwind] unwinding from signal handler

[Max Asbock]

Here is a question about unwinding from within a signal handler:

The architecture is either x86 or x86_64 where dwarf2 frame info is
used. By looking at elf files it looks like gcc only produces dwarf info
for the function prologues, but not the epilogues. If a signal is
received in the epilogue of a function just after the stack pointer has
been restored and the signal handler tries to unwind from there we could
get funny results because the IP still points to the current function
but the stack pointer points to the frame for the previous function. 
Any thoughts?

thanks,
max