xcode 2.2 creates 'virtually corrupt source files'
xcode 2.2 creates 'virtually corrupt source files'
- Subject: xcode 2.2 creates 'virtually corrupt source files'
- From: Mike Halpin <email@hidden>
- Date: Tue, 13 Dec 2005 12:35:56 -0800
Anyone seen this behavior, or know how to make it stop?
****
Since I did a clean checkout to an external drive, and started
building there, found that I get compile time errors which appear to
be the result of random garbage, or sometimes a string of '?' in
place of some of my code in one or more source files.
At first, I attributed this to some corruption which may have
occurred at the time I checked stuff out. I had been experimenting
with using fire wire ip, and thought that it may have somehow
introduced anomalies into the usage of the external fire wire disk
drive on which I was now building. That would be bad, but it turns
out, that's not what was happening.
I discontinued using firewire ip, and whenever I ran into one of
these corrupt files, I'd toss it, and update from cvs. However, I
later realized that I was encountering such a file when I had
previously completed a full build (after clean all). Therefore, I
had to consider that these files were being corrupted on an ongoing
basis.
Did a disk utility 'repair' of the volume, but it came up with no
repairs were needed.
I was getting ready to trash the latest bad file and then update from
cvs to get a clean copy, but decided to open it one more time to make
sure I was choosing the problem file. Double clicked on it and it
opened in Code Warrior (no surprise there, I have recently ported
from codewarrior, and all my sources are still tied to it as their
creator), BUT......
THE FILE WHEN VIEWED IN CODE WARRIOR WAS FINE!!!!!!!!
Next, I went into the finder, and selected the same file, and dropped
it on codewarrior, then on xcode. Now open in two windows, side by
side, xcode showed most of the code replaced by a long string of '?'.
IN code warrior, it was fine. Dropped the file on hexedit. Contents
looked fine. No strings of either ? or anything else that didn't
look like my code.
Clearly, xcode had somehow managed create a corrupted cache of data
from this file, and was displaying it to me whenever the file was
opened., and feeding it to the compiler.
To test this theory, I quit and restarted xcode, and sure enough, the
file now is fine, the build completes successfully.
I have seen this problem across multiple run/quit sessions with
xcode, and even across restarting my system. I fully expect to see
it again.
I will post a bug to Apple, but thought someone monitoring this list
might already know something about this.
--
------------------------------------------------------------------
Mike Halpin,
In the beginner's mind there are many possibilities. In the
expert's, there are few.
-- Shunryu Suzuki Roshi
------------------------------------------------------------------
_______________________________________________
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