d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

MFC r283652:

Browse Source 
Provide an unambiguous description of the potential hazard in calling
pthread_setspecific(3) from a key destructor.
This commit is contained in:
pkelsey 2015-06-04 04:50:52 +00:00
parent ada95a851c
commit 82415e4370
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
share/man/man3/pthread_setspecific.3
View File

@ -67,7 +67,10 @@ is undefined.
The
.Fn pthread_setspecific
function may be called from a thread-specific data destructor function,
however this may result in lost storage or infinite loops.
however this may result in lost storage or infinite loops if doing so
causes non-NULL key values to remain after
.Bq PTHREAD_DESTRUCTOR_ITERATIONS
iterations of destructor calls have been made.
.Sh RETURN VALUES
If successful, the
.Fn pthread_setspecific