Welcome to the MacNN Forums.

Ghoser777 · Feb 17, 2003, 09:06 PM

So I was working on my project called Dockless, and I was thinking I was pretty close to a 1.1 release, but then all of a sudden I get this crash whenever I start making NSFileManager calls:

BSDPathToIOMediaObject: unable to get IOKit master port: error 0xFFFFFFFF (-1)
dyld: /Users/fahrenba/Projects/Dockless/build/Dockless.app/Contents/MacOS/Dockless can't open library: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/LaunchServices (Too many open files, errno = 24)

Dockless has exited due to signal 5 (SIGTRAP).

I was worried that I had done something stupid and corrupted a framework or something, and I wanted to a clean install in the near future anyway, so I wiped my drive and zeroed it, then installed 10.2.3 off of the latest ADC mailing. I also recreated the Dockless project and imported all the files. But, much to my displeasure, the error persisted. So I'm lost for an explanation for why this is happening. If I remove the NSFileManager calls, the error goes away, but I really would prefer to find out what's going on instead of reinventing the wheel with a work around.

Thanks,
Matt Fahrenbacher

Angus_D · Feb 18, 2003, 10:20 AM

BSDPathToIOMediaObject: unable to get IOKit master port: error 0xFFFFFFFF (-1)

That's bizarre... And that's about all I can say :-/

Ghoser777 · Feb 18, 2003, 05:01 PM

Originally posted by Angus_D:
That's bizarre... And that's about all I can say :-/

Sigh...

Well, I guess there won't be a new version of Dockless for a while (or any other apps that I write that use NSFileManager...)

Matt Fahrenbacher

Ghoser777 · Feb 19, 2003, 05:44 PM

Hmmm... problem fixed. Note to self: don't do stuff with NDResourceFork (aka bizarre for loops)...

Matt Fahrenbacher

Angus_D · Feb 20, 2003, 04:36 AM

Care to elaborate?

Ghoser777 · Feb 20, 2003, 01:29 PM

Originally posted by Angus_D:
Care to elaborate?

If I must

Okay, I was trying to read in some data from a file's resource fork, but I didn't know the id, just the type. So I created a little for loop to iterate over id's 0 through 255 and see if there was any data. I'm pretty sure that was the stupidest way to go about that, but anyway, that's what I did.

I then conveniently forgot about that portion of code, and noticed that my NSFileManager calls were dieing. It seems that the two were related, although I think you'd be hard pressed to look at my code and figure out that this was the cause.

:hides head in shame:

Matt Fahrenbacher