On Wed, Sep 07, 2011 at 12:28:30PM +0200, Bernd Schmidt wrote:
> Question for Richard H.: What is this actually good for, other than
> presenting consistent information to dwarf2cfi? Do we actually expect
> code to unwind through the middle of an epilogue?
With -fasynchronous-unwind-tables and e.g. async cancellation enabled
pthread_signal may be handled anywhere. There have been several bug reports
e.g. against glibc, which is why Richard implemented the epilogue unwinding
on various targets. Additionally, if the debugger uses the unwind info,
when you step through the epilogue, you want precise unwind info too.
Jakub
