https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82141
--- Comment #35 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to simon from comment #33) > (In reply to Iain Sandoe from comment #32) > > > it doesn't make any difference if the libstdc++ is statically or dynamically > > linked, in fact > > It’s libgcc that causes the problem; with static libgcc, putting -lSystem > before -lgcc gets the proper unwinder (well, a _working_ unwinder, anyway). yes, we understand the problem - just not exactly where it's failing (e.g. if the unwinder is being asked to do something unsupported/able or if the unwinder is buggy .. or even if the unwind tables are being mangled by ld64, or if some combination of build parameters is causing two unwinders to get linked - which won't work).
