http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47558
--- Comment #29 from Iain Sandoe <iains at gcc dot gnu.org> 2011-02-01 23:53:31 UTC --- (In reply to comment #28) > Strangely this is insufficient to eliminate the crash (which still ends up in > the FSF libgcc unwinder)... > In fact, the only thing left which doesn't have the initial linkage on > /usr/lib/libgcc_s.1.dylib. Is the xplor executable itself. Well, the failure in that case seems plausible ... by linking the libraries '-flat_namespace' one has elected to have their dependencies satisfied from whatever order the libraries are presented by the next stage of linking... ... So, when you link the final exe (without -flat_namespace) if the FSF libgcc_s is presented first the dependent libs will use that - they have no information to tell them that the symbols should really come from somewhere else. If linking the final exe is done with -flat_namespace does it work?
