On Wed, 3 Feb 2010 11:30:15 -0500, "McLaughlin, Michael P."
said:
>In a multithreaded app using NSOperationQueue and targeting Leopard, I am
>having an inordinate amount of trouble communicating the results of the
>thread computations to the main thread which acts as an overall coordinator.
>
>thr
What Kyle and Jens said, but there is one particular cardiac action impaired
horse that I wanted to flog...
On Feb 3, 2010, at 8:30 AM, McLaughlin, Michael P. wrote:
> I thought that this should all be correct but somehow it crashes, at times
> immediately, at other times only when everything is
On Feb 3, 2010, at 8:30 AM, McLaughlin, Michael P. wrote:
but their own. I have to pass these filled structures back to the
main
thread upon completion. The last thing each thread does is
postNotificationName to the main thread saying that it is ready to
return
lots of data which it does
Am 03.02.2010 um 17:30 schrieb McLaughlin, Michael P.:
> Could someone recommend the "best" (most robust) way to pass back data from
> threads to the main thread? Is there a good way to probe crashes such as
> these? Right now, I cannot even tell where the error is really occurring.
Try
- (vo
On Wed, Feb 3, 2010 at 8:30 AM, McLaughlin, Michael P. wrote:
> In a multithreaded app using NSOperationQueue and targeting Leopard, I am
> having an inordinate amount of trouble communicating the results of the
> thread computations to the main thread which acts as an overall coordinator.
Welcom
In a multithreaded app using NSOperationQueue and targeting Leopard, I am
having an inordinate amount of trouble communicating the results of the
thread computations to the main thread which acts as an overall coordinator.
Specifically, I am getting obscure and sporadic crashes (about 10 percent o
