Re: Yet another problem with NSTask and NSPipe
Re: Yet another problem with NSTask and NSPipe
- Subject: Re: Yet another problem with NSTask and NSPipe
- From: Uli Kusterer <email@hidden>
- Date: Sun, 22 Apr 2007 15:39:20 +0200
Am 22.04.2007 um 15:03 schrieb Dragan Milić:
Isn't this a little odd? I'd expect you to be using /usr/bin/
hdiutil (or whatever) as the launch path, and not pass hdiutil as
the first parameter.
One can use both approaches, not really related to the problem I have.
If you say so. Just pointing out possible points of breakage.
What I do is unregistering an object as observer from all entries
that specify NSFileHandleReadCompletionNotification as notification
name, hence including my file handle I previously registered the
object with. Again, one can use both approaches in this case, not
related to the problem.
I vaguely remember there used to be a bug where you had to have the
two balanced. I.e. if you registered with a notification object, you
had to unregister with one, too, or something got out of whack. I'd
presume that's been fixed, but it might be worth a shot. If it's been
broken once, it may be broken still.
Have you tried testing it without the notification? What happens if
you use readDataToEndOfFile: or something like that? It might not
solve your problem, but at least it would help locating the actual
point where the error sits.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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