Re: Mac OS 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
Re: Mac OS 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- Subject: Re: Mac OS 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- From: Quinn <email@hidden>
- Date: Tue, 19 Jul 2005 13:33:03 +0100
At 10:03 +0530 19/7/05, Karunakar Reddy G wrote:
Basically I am using for creating a task and killing a task,
For creating a Task, first I create a thread using IOCreateThread,
then I bind the thread using thread_bind(),
Why are you binding the thread to a particular CPU?
Regardless, there isn't any way bind a thread to a particular CPU
using supported KPIs. The thread_bind routine continues to exist,
and is exported by the kernel, but you can't access it without
linking to the entire kernel, which is not appropriate for a shrink
wrap product.
For killing a task, I kill current running tasks using thread_terminate_self()
Is there a reason you can't use IOExitThread? It's sitting in the
"IOLib.h" header right next to IOCreateThread (-:
One more thing, functions thread_bind() and thread_terminate_self()
are defined in header files in old developer kit (
April2002Dev.tools).But these functions are removed in Xcode 2.0
developer tools
Traced in this path:
System/Library/Frameworks/Kernel.Framework/Versions/A/Headers
Is there any alternate way to handle using KPIs, instead of using
these functions?
As part of the KPI effort, the Kernel framework headers only include
functions that are supported (and thus part of a KPI). If you decide
to call unsupported functions, you're pretty much on your own (after
all, that's the definition of "unsupported").
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden