Article:		OS 9, Mine, All Mine
Subject:		Builds failing
Date:		2004-07-23 16:53:09
From:		dgroulx
If you are having issues with builds failing on OS X while using XCode, I have been having the same problem, however there is an easier solution than reinstalling the entire OS. Quit Xcode, open up the terminal and type 'defaults delete com.apple.Xcode'. That has fixed it for me every time.

Showing messages 1 through 3 of 3.

• Builds failing
  2004-07-24 18:03:21  khagler [View]
  
  
  The build failures were with Codewarrior, not XCode. We've switched to XCode for our newest project, but so far I've only built it twice--not enough to form an opinion on its reliability (both builds were without incident).
  
  I've made a note of your command for future reference, though. Thanks!
• Builds failing
  2004-07-24 21:51:44  qu1j0t3 [View]
  
  
  In my experience the cause of this type of failure, under OS X, is bad RAM. Compilers exercise memory more than most other workloads, and have many built-in integrity checks on their data structures (unlike many applications and even filesystems). Compilers also have a very high memory and CPU utilisation. For all these reasons memory problems are likely to be exposed this way and your symptoms strongly suggest this is the culprit.
  
  Try Charles Cazabon's memtester. I have used this tool to confirm memory problems after seeing otherwise inexplicable CodeWarrior and gcc compile crashes. (You should run this tool in single user mode, and do not attempt to test more than about 90% of RAM as this will fatally starve the Darwin VM system.)
• memtest for OS X
  2004-07-26 17:06:18  hayne [View]
  
  
  There is an updated version of memtest, built for OS X and with some severe bugs corrected, here:
  http://friskythecat.tripod.com/