On Jan 24, 2008 1:12 PM, Terry Lambert <email@hidden> wrote:
> Please see my other posting. You are not fixing your underlying
> problem here.
>
> My personal suggested fix would be to marshal the data to a single
> thread for disposition. Then your limit will be however much data you
> can jam down the drain pipe plus however much data you are willing to
> internally queue in your application in the marshalling process.
>
I'm only logging a few lines - maybe 500 characters in total - so I
can't see how I'd be overloading the queue. Even if I did, presumably
the write() call ought to return eventually?
I haven't yet been able to reproduce this outside of Xcode - it's
tempting to blame it on an oddity in Xcode's run log and forget about
it...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
