I have an NSDocument based application. Starting in 10.5.1 users
have been been reporting that their document changes could not be
saved, and that the following has been reported to the Console:
"NSDocument called FSPathReplaceObject() and -39 was returned."
-39 is eofErr.
I cannot reproduce this myself.
I've seen in the debugger that FSPathReplaceObject is called from
[NSDocument saveDocument:]. My code does not directly call
FSPathReplaceObject.
The users experiencing problems have fixed their permissions and
rebooted multiple times. If they do a Save As..., the users never
have this problem again with the new file, but continue to have the
problem with the old file **in the same directory**.
The files are never larger than a few hundred K, and are written
upon request in my NSDocument subclass by [myNSData writeToFile:
atomically:YES], which returns YES.
Any ideas on why FSPathReplaceObject is returning -39 (eofErr), but
only on some systems? And only for a specific file?