Re: my filesystem vs Finder. "error -50" what does it mean?
Re: my filesystem vs Finder. "error -50" what does it mean?
- Subject: Re: my filesystem vs Finder. "error -50" what does it mean?
- From: Jim Luther <email@hidden>
- Date: Mon, 16 Apr 2012 14:29:35 -0700
On Apr 16, 2012, at 2:06 PM, Anatol Pomozov <email@hidden> wrote:
> Hi,
>
> I am working on my filesystem (fuse4x - fuse implementation for macosx). And sometimes I have bugs in it that lead to Finder errors.
The Finder is an application and it is just reporting an error condition -- it may or may not be generating the -50 error.
> For example Finder popups with "error -50" and I suspect that it is related to setattr() function, probably size of the written file. Finder does not like something that my filesystem does.
-50 is defined as paramErr in MacErrors.h. It is kind of a "catch all" error code that is returned when either (1) a bad argument is passed to an API or (2) an unexpected result comes back from a POSIX/BSD request and it cannot be translated to something better.
> And I want to know what *exactly* Finder does not like.
It's not that easy (unless your working on the Finder team).
fs_usage(1) might be useful for getting you close to the problem -- it will let you see the file system requests made by the Finder process.
> Is there any table that explains all the "error -N" popup errors? Is this part of Finder open so I can read it?
<CarbonCore/MacErrors.h> has most of them. Apple stopped putting new error codes there some time ago and so newer error codes are spread throughout various headers where they are defined by the part of the OS that uses them.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden