site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com <quote> Mac OS X is just broken. 10.5 apparently passed the VSTH suite, which simply means that the test suite has missed a few more relatively obvious test cases. </quote> "In particular, no test suite can detect every possible way that an implementation can be non-conforming." <quote> I would seem to me that Apple should correct the problem, once reported, by its next Open Brand Certificate renewal date, which si 18 May 2008.[sic] </quote> <quote> Apple has an obligation to correct any reported non-conformities "within the prescribed timescale", regardless of what may not be detected by a test suite. (See http://www.opengroup.org/openbrand/ .)" </quote> And, quoting from <http://www.opengroup.org/openbrand/>: "If ... the non-conformance is not corrected in the predefined timescale, then the Product Registration, and the ability to use the trademark, will be lost." <quote> It would, in fact, be INCORRECT to call read(), or most other POSIX functions, with asynchronous cancel enabled. From POSIX, "The pthread_cancel( ), pthread_setcancelstate( ), and pthread_setcanceltype( ) functions are defined to be async-cancel safe. No other functions in this volume of POSIX.1-200x are required to be async-cancel-safe." </quote> Regards, _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... I just added the following information to my bug report (misspellings and all...): I brought this up on the austin-group-l mailing list (Nov 23 2007, Item 11231 "A question about cancellation points" on https://www.opengroup.org/sophocles/show_archive.tpl?listname=austin-group-l) . Presumably the Austin list members have more experience than most in judging in matters related to SUSv3 conformance. The consensus seems to be that the current Mac OS 10.5 behavior does not conform to SUSvw3 and that: The thread also points out that the behavior with PTHREAD_CANCEL_ASYNCHRONOUS is irrelevant since: This email sent to site_archiver@lists.apple.com