I am porting a (hairy) Solaris app to OS X which makes heavy use of the
pthread libraries (blocking, unblocking, cond vars, mutexes, etc.). When
I try to have the main thread sleep somehow (I have tried sleep(), sem_wait(),
pthread_cond_wait()) after spawning and starting all the other pthreads,
the program just pegs the CPU when the main thread gets to this call.
Is there something in the pthread libs which might not yet be complete
which would cause something like this? Is this a matter of setting
priorities correctly? Any other bells going off because of this behavior?
TIA.
-Conrad
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
