Bug w/NSTask and NSPipe? (was: Debugging problems)
Bug w/NSTask and NSPipe? (was: Debugging problems)
- Subject: Bug w/NSTask and NSPipe? (was: Debugging problems)
- From: Michael Mulligan <email@hidden>
- Date: Mon, 28 Mar 2005 19:49:58 -0500
In case this helps anybody in the future:
The cause of the mysterious exception:
*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value
*** Uncaught exception: <NSInvalidArgumentException> ***
-[NSCFDictionary setObject:forKey:]: attempt to insert nil value
The NSPipe is null some times (but working fine other times)! Here's
all of the code that involves the pipe (which definitely doesn't seem
to shed much light on things):
(this is all just your standard fare run-an-NSTask code)
NSPipe *sopipe=[[NSPipe alloc] init];
//...
if(sopipe==nil)
NSLog(@"uh oh!");
[shell setStandardOutput:sopipe];
handle=[sopipe fileHandleForReading];
//...
I'm thinking this is a bug worth filing?
-Mike
__________
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me
spread!
__________
On Mar 28, 2005, at 6:52 PM, Michael Mulligan wrote:
Also, Ondra, I'd tried your suggestion as for holding off on releasing
the NSTask and NSPipe, but still no dice--it appears as if the
offensive line might be handle=[sopipe fileHandleForReading] though...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden