http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55956
--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> --- This is another manifestation of 44107. The installed libgcc_s on darwin9 has an unwinder that does not recognise modern gcc output. The testsuite usually hides this by setting DYLD_LIBRARY_PATH/LD_LIBRARY_PATH to point to the newly-built libgcc_s (which, of course, works). It appears that the setting of DYLD_LIBRARY_PATH is not happening (or happening incorrectly) for the case that the testsuite (at least the acats portion) is run from the gcc dir. I have not tried to determine where the problem occurs or if it manifests in the same manner on Linux - since folks don't seem too concerned about it. Of course, it is potentially relevant that testing might be using different components depending on where it's invoked from. (I don't personally propose to do anything about this).
