Re: really weird move file problem - copy fails also, more datapoints
Re: really weird move file problem - copy fails also, more datapoints
- Subject: Re: really weird move file problem - copy fails also, more datapoints
- From: Dave Hersey <email@hidden>
- Date: Fri, 21 Sep 2007 16:25:10 -0400
Sounds like a good first step. Again, if your application is actually
locking up (per your first message), then this is more than just a
file manager copy failure (unless the lockup happens later because
the dest file is invalid or something.) No crash logs, huh?
If the scaled back version still fails, keep in mind that there could
still be something more going on that's causing the problem. Is any
of your code threaded by any chance? That could open entirely new
possibilities--autorelease pools, calls/code that isn't threadsafe, etc.
In any case, good luck . :)
- Dave
On Sep 21, 2007, at 4:04 PM, Jaime Magiera wrote:
On Sep 21, 2007, at 3:23 PM, I. Savant wrote:
Ah - then it's rather improbable there's a hardware issue. See the
others' comments about the validity of the paths themselves.
Yeah.
I have been keeping track of the paths. They are correct and have
no special characters (that was one of the first things I had him
do, was make sure all the paths involved had no special
characters). Now, since the file is partially getting created in
the destination location, wouldn't that preclude paths as an issue
though?
Here's a weird thing: I met up with him to be sure of what was
going on. When he tried to use the software in front of me, it
could *not* copy even to the same partition. So, it doesn't seem to
copy to any partition or device. We tried setting the destination
to my laptop in target disk mode. Same error. I ran the software
from my machine and set the file destination to be *his* laptop in
target disk mode. That worked fine. We both have the same MacBook
Pros (though he has his /Users on a separate partition).
Here's how I'm going to troubleshoot this evening...
I've just given him a build that has the method modifying the file
commented out. In other words, it's just going to copy from tmp out
to his selected destination. This will tell me unequivocally if
it's just the copying, or if its something in copying *after* the
method modifies the file (the method adds a QT Track atom and adds
data to the MDAT atom). Note that the method works on all the
other machines I've tried. The movies play fine with all the right
data. crazy.
I'll keep you folks abreast of the situation as it develops.
thanks!!!!!
Jaime Magiera
Sensory Research
http://www.sensoryresearch.net
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
40herseyweb.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden