site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Organization: Swedish Institute of Computer Science This is when compiling user-level programs. What exectly is supposed to change when setting _APPLE_C_SOURCE? I realize that this causes a new version of pthread_cancel to be called. However, the real problem is that the POSIX mandated thread cancellation points are missing, e.g. in read and write. Is there any way, in Darwin, to interrupt a thread that is blocking in a system call like read? pthread_cancel does not seem to work, even if the code is compiled with -D_APPLE_C_SOURCE. PS. I joined the list late so this message may not show up in the right thread. Regards, -- Per Mildner Per.Mildner@sics.se Swedish Institute of Computer Science _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On 8-May-06, at 16:08 , Matt Watson wrote: On May 8, 2006, at 12:59 PM, Andre-John Mas wrote:
On May 8, 2006, at 12:45 PM, Andre-John Mas wrote:
Could anyone tell me whether pthread_cancel() is planned to be
implemented properly in a future version of Darwin? From what I
understand the current implementation does not conform to the
posix implementation.
If you compile with _APPLE_C_SOURCE, _POSIX_C_SOURCE or
_XOPEN_SOURCE, the implementation should behave as you want.
Thanks. Just one question are these for my applications or for
compiling the kernel?
matt. This email sent to site_archiver@lists.apple.com