GDB: data formatters temporarily unavailable
GDB: data formatters temporarily unavailable
- Subject: GDB: data formatters temporarily unavailable
- From: Teri Pettit <email@hidden>
- Date: Fri, 01 Jul 2011 16:26:58 -0700
- Acceptlanguage: en-US
- Thread-topic: data formatters temporarily unavailable
Just today I started getting the following error when I try to debug my app (XCode 3.2.5, OS 10.6.7):
GDB: Data Formatters temporarily unavailable, will re-try after a 'continue'. (Not safe to call dlopen at this time).
#0 0x8fe01065 in __dyld_dyld_fatal_error
#1 0x8fe04fa5 in __dyld__ZN4dyld4haltEPKc
#2 0x8fe0796b in __dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_
#3 0x8fe018b1 in __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKcl
#4 0x8fe01057 in __dyld__dyld_start
Everything compiles and links fine.
The error happens about one second after it displays 'GDB: Loading program into the debugger...'
If I hit Continue, it just stays at the same line in the assembly.
If I turn off Variables View>Use Data Formatters and continue, it gets an immediate access violation at the same assembly code line. The same happens if I do Run instead of Debug.
The application has not started gotten anywhere near starting yet, it has just barely begun to load the program. (Usually it takes several minutes to load.)
I googled on the error message, and the threads that came up were mostly from iPhone app developers, and typical solutions were making the app consume less memory such as reducing the size of global arrays.
It is true that the app is extremely large (826 source files just in the core app project, plus dozens of large shared libraries and over 200 plugins), but that has never been a problem before. (Well, stepping through in the debugger is always excruciating slow, like 10-15 seconds per step next and about a minute to step into a function, and data formatting often times out, but at least it runs.)
I doubt that app footprint is the problem because:
(1) Nothing significant has changed in the app's memory usage since the last time I was able to debug it.
(2) I'm running fewer other apps simultaneously than I usually do. (I've shut down everything except Safari and XCode.)
(3) It happens so quickly that it can't have gotten very far into the loading process at all.
So it sounds more like some problem with the debugger or some project incompatibility that is immediately detected.
This is a team project under source control. None of the other engineers has reported a recent problem running under the debugger.
I've tried doing a full Clean rebuild including dependencies and precompiled headers, and nothing changed.
Any ideas, hints about how to refine the problem, etc?
(All the other dev team members are in India and it's 4 am Saturday morning there, so I expect I'll get faster response asking on a list with US distribution.)
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 5 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden