Hi, On Fri, 11 Nov 2011, Ulrich Weigand wrote:
> I haven't fully debugged it yet, but it seems to be related to the > linked list of unwind contexts that are maintained by the SjLj logic. > During unwinding, those are pulled off the list one by one; it seems the > routines that do that don't expect that new contexts for the _Unwind > routines themselves are being implicitly pushed onto that list while the > unwinding happens ... > > > 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 :-/ > > I guess one attempt might be to build the unwinder files with > -funwind-tables instead of -fexceptions ... Hmm, that could work. Or marking all routines that the unwinder calls as nothrow. Ciao, Michael.
