| Chris,
Thanks for the info. Things were getting so crazy I was willing to look into the bad RAM theory. I had actually upgraded the RAM on my development machine at about the time I upgraded to Xcode 3.2. In fact I did the RAM upgrade because I noticed that 2GB just wasn't enough to do development and use Instruments. However I had run all sorts of RAM tests when I first installed it with no issues at all. And since then I haven't noticed any other problems other than with Xcode. So I did another more thorough set of RAM tests this week to see if there are RAM issues. I spent one night running memtest and another day running Apple Hardware Test. With over 8 hours of testing for each tool I got no errors. So nothing conclusive. I may try to reinstall the old RAM and see what happens.
Yes, rolling back to previous versions of my projects from Subversion will build. However, anytime I tried to modify them I started getting strange errors.
There's obviously evidence of corruption. The question is what caused it and when. I'm theorizing it has to do with moving to Xcode 3.2 and/or changing to LLVM. But no one else seems to experience the problems I've seen. So it could be the RAM issue. I'll have to continue tracking this down.
BTW, I am not setting any build settings using /tmp. I don't know why the build tools were trying to look there.
Also, is there a way to get a crash log when any of the compiler tools crash during a build? For example ld or gcc. All I see is an error message in the Xcode logs. I don't see anything in the system Console logs.
I haven't filed any bugs yet since I'm still trying to track what's happening. I also wouldn't be able to supply much more information in my bug report since I can't send my projects files (confidentiality issues). And I don't think I have much more time to exhaustively change each project setting until I find the problems again. I'll look into what I can and if I find anything conclusive I'll write that up.
After recreating all my projects from scratch in Xcode 3.1 and using a different build machine, I think I did find a bug with LLVM on PPC. When attempting to display a stack crawl I'm getting errors from GDB during debugging of the form:
Die: DW_TAG_member (abbrev = 52, offset = 24123) has children: FALSE attributes: DW_AT_type (DW_FORM_ref4) constant ref: 24011 (adjusted) DW_AT_byte_size (DW_FORM_data1) constant: 8 DW_AT_name (DW_FORM_string) string: "size" DW_AT_decl_file (DW_FORM_data1) constant: 53 DW_AT_decl_line (DW_FORM_data1) constant: 58 Dwarf Error: Cannot find type of die [in module / /Full/Path/To/My/Shared/Library
This would appear to be a compiler bug. Are there known issues with LLVM GCC and PowerPC?
Doug Hill
On Jan 26, 2010, at 5:19 PM, Chris Espinosa wrote: On Jan 26, 2010, at 11:25 AM, Doug Hill wrote: I'm writing because I've been having nothing but troubles with getting my Xcode projects to build. I'm getting so many strange errors it's freaky:
- Compiler will crash (bus error or other errors)
This is fairly to very rare. Which compiler? Crashes building what? (ObjC, C++, ...?) - Linker will crash (similar issues)
This is extremely rare. - Xcode throws exceptions when the project is opened, with the Continue/Quit dialog. Usually complaining about a problem with a child container.
Could imply project-file corruption. Does rolling back to an earlier project version in your repository fix this?
I hope you've filed crash reports on all of these. (Nothing with your name on it jumps out at me at the moment.) - Random problems like this one:
"duplicate symbol SomeSymbolOrAnother() in /tmp/lto.o and /Path/To/My/Build/Folder/build/ProjectName.build/Release/ProjectName.build/Objects-normal/ppc/sourcefilename.o"
This will just pop up randomly after building previously.
Are you aware of anything in your project intentionally building into /tmp ? Because Xcode doesn't. /tmp is not a particularly useful place to use for an intermediates directory, for a couple of reasons.
One thing, and this is experience, not buck-passing: if you are having sudden, pervasive, and mysterious errors in a number of subsystems, check your RAM. Xcode is a memory-intensive, processor-intensive app that pushes system memory to limits that other apps don't. If you have borderline flaky system RAM, an overheating machine, etc. the problem will show up as random crashes during building way before you notice it in, say, reading email or browsing the Web.
Crash logs and build transcripts attached to bugs are much more helpful to us to help you diagnose odd cases like this.
Chris
|