Debugging Stdout
Debugging Stdout
- Subject: Debugging Stdout
- From: Ronnie O <email@hidden>
- Date: Mon, 3 Oct 2005 21:20:46 -0400
Hello all,
Can anyone give me some ideas for debugging a failed data return from
stdout? I have code using NSTask setup to pipe text into a program and have
the program echo the text data back. The code I put together works fine for
a perl script that i put together, but I am not getting the data returned
when i pipe to a c program. I replaced a readInBackgroundAndNotify with a
waitForDataInBackgroundAndNotify and I am getting notification of available
data for the perl call but not the c call. When I run the piped command of
the c program from the command line, the data is piped out to the screen. I
am calling the same program from my cocoa app with a flag to pipe output to
stdout, but I just can't get any data through the pipe. Are there any
obvious reasons why my cocoa app would see data from stdout differently from
a perl or c program? Like I said, I am using the same code for both calls
and I know data is getting into both tasks from the debug files. I just
don't know how to debug any more finely. I do know that an
NSFileHandleConnectionAcceptedNotification is being posted in both cases, so
the task end of the pipe is being seen by the task. I just don't know where
the missing link between stdout and the task end is. How can I find where
stdout is going? Thanks all!
...........
Ronnie
_______________________________________________
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