https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
Pierre Ossman <ossman at cendio dot se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ossman at cendio dot se
--- Comment #28 from Pierre Ossman <ossman at cendio dot se> ---
I'd like to reopen this issue as we are still seeing this with as new gcc as
4.8.4 (we've been unable to build anything newer). Unfortunately I do not seem
to have the access rights to reopen the bug. Help?
We've primarily been using 4.6.4 but we also did a test build with 4.8.4 to see
if a newer gcc solved the issue. Unfortunately the problem is the same, with
the same stack trace.
We have however found that the problem seems to be an incompatibility between
OS X's unwinder and gcc's (something we found various other gcc bugs and
mailing lists discussions on).
Or normal way of doing things is to statically link libstdc++ and libgcc_eh.
This results in crashing programs. If we inject libSystem before libgcc_eh
however, we get the system unwind routines and the program works fine. This is
not quite the same as the previous cases mentioned on this bug, but the dumps
show that a custom libgcc_s is being used so it should be equivalent.
Not sure what the proper fix is but our plan is to bastardise gcc a bit and
remove the unwinding routines to make sure the system ones are always used.
