2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved.
3 .\" Copyright (c) 2001, the Institute of Electrical and Electronics Engineers, Inc. and The Open Group. All Rights Reserved.
4 .\" Copyright 1991, 1992, 1994, The X/Open Company Ltd.
5 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
6 .\" http://www.opengroup.org/bookstore/.
7 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
8 .\" This notice shall appear on any product containing this material.
9 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
10 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
11 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
12 .TH PTHREAD_GETSPECIFIC 3C "Mar 23, 2005"
14 pthread_getspecific, pthread_setspecific \- manage thread-specific data
18 cc -mt [ \fIflag\fR... ] \fIfile\fR... -lpthread [ \fIlibrary\fR... ]
21 \fBint\fR \fBpthread_setspecific\fR(\fBpthread_key_t\fR \fIkey\fR, \fBconst void *\fR\fIvalue\fR);
26 \fBvoid *\fR\fBpthread_getspecific\fR(\fBpthread_key_t\fR \fIkey\fR);
32 The \fBpthread_setspecific()\fR function associates a thread-specific
33 \fIvalue\fR with a \fIkey\fR obtained by way of a previous call to
34 \fBpthread_key_create()\fR. Different threads may bind different values to the
35 same key. These values are typically pointers to blocks of dynamically
36 allocated memory that have been reserved for use by the calling thread.
39 The \fBpthread_getspecific()\fR function returns the value currently bound to
40 the specified \fIkey\fR on behalf of the calling thread.
43 The effect of calling \fBpthread_setspecific()\fR or
44 \fBpthread_getspecific()\fR with a \fIkey\fR value not obtained from
45 \fBpthread_key_create()\fR or after \fIkey\fR has been deleted with
46 \fBpthread_key_delete()\fR is undefined.
49 Both \fBpthread_setspecific()\fR and \fBpthread_getspecific()\fR may be called
50 from a thread-specific data destructor function. However, calling
51 \fBpthread_setspecific()\fR from a destructor may result in lost storage or
56 The \fBpthread_getspecific()\fR function returns the thread-specific data
57 value associated with the given \fIkey\fR. If no thread-specific data value is
58 associated with \fIkey\fR, then the value \fINULL\fR is returned.
61 Upon successful completion, the \fBpthread_setspecific()\fR function returns
62 \fB0\fR. Otherwise, an error number is returned to indicate the error.
66 The \fBpthread_setspecific()\fR function will fail if:
73 Insufficient memory exists to associate the value with the key.
78 The \fBpthread_setspecific()\fR function may fail if:
85 The key value is invalid.
90 The \fBpthread_getspecific()\fR function does not return errors.
94 See \fBattributes\fR(5) for descriptions of the following attributes:
102 ATTRIBUTE TYPE ATTRIBUTE VALUE
104 Interface Stability Standard
112 \fBpthread_key_create\fR(3C), \fBattributes\fR(5), \fBstandards\fR(5)