MirOS Manual: pthread_setspecific(3)

PTHREAD_SETSPECIFIC(3)     BSD Programmer's Manual      PTHREAD_SETSPECIFIC(3)

NAME

     pthread_setspecific - set a thread-specific data value

SYNOPSIS

     #include <pthread.h>

     int
     pthread_setspecific(pthread_key_t key, const void *value);

DESCRIPTION

     The pthread_setspecific() function associates a thread-specific value
     with a key obtained via a previous call to pthread_key_create(). Dif-
     ferent threads may bind different values to the same key. These values
     are typically pointers to blocks of dynamically allocated memory that
     have been reserved for use by the calling thread.

     The effect of calling pthread_setspecific() with a key value not obtained
     from pthread_key_create() or after key has been deleted with
     pthread_key_delete() is undefined.

     pthread_setspecific() may be called from a thread-specific data destruc-
     tor function; however, this may result in lost storage or infinite loops.

RETURN VALUES

     If successful, the pthread_setspecific() function will return zero. Oth-
     erwise an error number will be returned to indicate the error.

ERRORS

     pthread_setspecific() will fail if:

     [ENOMEM]      Insufficient memory exists to associate the value with the
                   key.

     [EINVAL]      The key value is invalid.

SEE ALSO

     pthread_getspecific(3), pthread_key_create(3), pthread_key_delete(3)

STANDARDS

     pthread_setspecific() conforms to ISO/IEC 9945-1:1996 ("POSIX").

MirOS BSD #10-current           April 4, 1996                                1

Generated on 2014-04-02 20:57:59 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.