Hi, On Fri, 11 Nov 2011, Ulrich Weigand wrote:
> One reason why this happens is that the unwind*.c files are specifically > built with -fexception. I think this is for the benefit of the DWARF > unwinder, to ensure CFI records are available for those routines. Except for the routines that start the backtracing (e.g. _Unwind_RaiseException) I don't see how descriptors for them are useful. But even those use local variables that would be handled by the scope-end clobbers. Hmpf. Why does the sjlj unwinder go into an endless loop, and only in _Resume, not already in the first phase (i.e. from _RaiseException), which also iterates over the backtrace. If we can't fix the sjlj unwinder to cope with this situation I don't see much choice than implementing a command line flag disabling the clobbers and use that for compiling the unwinder :-/ Ciao, Michael.
