My "short" answer:
You may have noticed this already, but just in case:
First of all, even when you see that error, (assuming that you click past it and continue), then you should still be able to use 99% of the debugging features in Xcode. In other words, that error means that only a very small, specific portion of the debugger is "broken" for a given debugging session. It does not mean that debugging is completely down and/or impossible for the given program-execution.
Given the above fact, if you simply want to get rid of the error and do not care whether Custom Data Formatters are working or not, then REMOVE the check-mark next to the following menu item:
- Run -> Variables View -> Enable Data Formatters
My "long" answer:
The developers in my office had been experiencing this very same Xcode error for quite a while until someone discovered that some third party libraries were the cause.
In our case, this error was happening only for projects using wxWidgets. I am not meaning to imply that usage of wxWidgets is the only possible cause. I am only trying to put forth more information that might lead to the right solution for your case.
Also of interest: we (in my office) were getting this error without any use or presence of any .gdbinit file whatsoever.
It turns out that the "property" of wxWidgets that made it trigger this error was related to a "custom/generic" implementation of "dlopen." Prior to Mac OS X 10.3,
dlopen was not provided within the operating system, so apparently some libraries coded their own versions. When such libraries are being used, then apparently the dlopen call that tries to open PBGDBIntrospectionSupport.A.dylib can fail.
Read through the comments on this sourceforge patch submission to learn even further details about dlopen in 10.3 and beyond.
Also, here is another related link:
Message on the Xcode users mailing list about PBGDBIntrospectionSupport and Custom Data Formatters