Defect report from : Loic Domaigne , Personal Interest
(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
@ page 1125 line 35289 section pthread_rwlockattr_destroy comment
{pthread_rwlockattr_init, issue EBUSY}
Problem:
Edition of Specification (Year): 2003
Defect code : 2. Omission
References are given against TC1.
In lines 35281-35282, it is said that:
| results are undefined if pthread_rwlockattr_init() is called
| specifying an already initialized attr attributes object.
However, the standard doesn't define any optional checking for this error.
Action:
At l35289-35294 (§ERRORS), add:
The pthread_rwlockattr_init() may fail if:
[EBUSY]
The implementation has detected an attempt to reinitialize the
read-write lock attribute object referenced by attr, a previously
initialized, but not yet destroyed, attribute object.
|