Barry Andrews wrote: > Andrew Haley wrote: >> >> Yes, it is always true AFAIAA. The unwinder reads the data lazily, >> so unless it actually finds a stack frame belonging to code that has >> no unwinder data, that should have no effect. The instant the unwinder >> sees a frame that it can't unwind, it will abort: there is nothing >> else it can do. >> >> Note this: the abort is from within the unwinder, WHILE IT IS >> TRYING TO UNWIND A ROUTINE WITH NO UNWINDER DATA. So, you have >> to try to find out why that is happening. >> >> gdb is your friend here. >> > And that's why it aborts for me. There is no unwinder data at all. I'll > keep digging, but there are lots of internals here to debug. OK, so you have to look at a gdb backtrace to see which routine with no unwinder data is being unwound. >>> Is there no work around for this? It seems so very strange to me. >>> >> >> Compile with -fexceptions. >> > Yeah, I have that. Doesn't help. Did it work for you? Yes, always. Andrew.
