On Jul 7, 2005, at Thu, Jul 7, 1:11 29 PM, David Ewing wrote:
If the file is bad, certainly replace it. But it's not at all obvious how it could have gotten corrupted.
Nevertheless, the console message is quite clear, and when I replaced the file, the problem went away. Note that this problem was not resolved by:
-restarting
-trashing xcode prefs
Xcode only ever reads from the file.
I think the only thing we can say with confidence is that Xcode is only *supposed* to read from the file. But software sometimes has bugs. Is there any likelihood that anything else would even read this file, much less try to write to it?
Do you have any third party plug-ins that might have changed the file?
No third party plug-ins at all. I'm running Xcode 2.1 as installed.
Or perhaps there's some disk corruption. It might be worth checking the disk with Disk Utility.
Already did that before I thought to check the console log- no errors found.
1. that Xcode is (erroneously) writing to this file when it should only be reading it, and that this is related somehow to the preferences for General:Layout and General:Editing since these are the *only* things I changed from the default configuration as installed when the problem manifested.
2. There is a bug in the XML parser/Old-style plist parser.