http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> 2010-11-26 21:32:39 UTC --- Notes: (temporary work-arounds) 1. for Fortran, one can effect a fix by altering the dsymutil spec in config/darwin.h and config/darwin9.h thus: .c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm|.s|.f|.f90|.f95|.f03|.f77|.for|.F|.F90|.F95|.F03: 2. The generic 'failing' is that the spec is looking at only the last item on the c/l -- if that happens to be a source file, the dSYM will be generated. There isn't a generic facility to recognize *any* source file and post a flag (perhaps something worth considering in 4.7). So, you need to make at least one of your source files the last entry on the c/l. 3. To avoid the need for the dSYM at all -- if all you want to do is to debug locally -- just use "-save-temps". 4. Note that there are incompatibilities between the current debug output of FSF gcc and dsymutil - we cannot 'fix' dsymutil as it is closed source. At present, these cause irritating but harmless warnings.
