![]() |
![]() |
| ||||||||
Return Valuespthread_detach() returns zero when it completes successfully. Any other return value indicates that an error occurred. When any of the following conditions is detected, pthread_detach() fails and returns the corresponding value.
Create a Key for Thread-Specific DataSingle-threaded C programs have two basic classes of data--local data and global data. For multithreaded C programs a third class is added--thread-specific data (TSD). This is very much like global data, except that it is private to a thread. Thread-specific data is maintained on a per-thread basis. TSD is the only way to define and refer to data that is private to a thread. Each thread-specific data item is associated with a key that is global to all threads in the process. Using the key, a thread can access a pointer (void *) that is maintained per-thread. pthread_key_create(3THR)Use pthread_key_create(3THR) to allocate a key that is used to identify thread-specific data in a process. The key is global to all threads in the process, and all threads initially have the value NULL associated with the key when it is created. Call pthread_key_create() once for each key before using the key. There is no implicit synchronization. Once a key has been created, each thread can bind a value to the key. The values are specific to the threads and are maintained for each thread independently. The per-thread binding is deallocated when a thread terminates if the key was created with a destructor function.
When pthread_key_create() returns successfully, the allocated key is stored in the location pointed to by key. The caller must ensure that the storage and access to this key are properly synchronized. An optional destructor function, destructor, can be used to free stale storage. When a key has a non-NULL destructor function and the thread has a non-NULL value associated with that key, the destructor function is called with the current associated value when the thread exits. The order in which the destructor functions are called is unspecified. Return Valuespthread_key_create() returns zero after completing successfully. Any other return value indicates that an error occurred. When any of the following conditions occur, pthread_key_create() fails and returns the corresponding value.
Delete the Thread-Specific Data Keypthread_key_delete(3THR)Use pthread_key_delete(3THR) to destroy an existing thread-specific data key. Any memory associated with the key can be freed because the key has been invalidated and will return an error if ever referenced. There is no comparable function in Solaris threads.
Once a key has been deleted, any reference to it with the pthread_setspecific() or pthread_getspecific() call yields undefined results. It is the responsibility of the programmer to free any thread-specific resources before calling the delete function. This function does not invoke any of the destructors. Return Valuespthread_key_delete() returns zero after completing successfully. Any other return value indicates that an error occurred. When the following condition occurs, pthread_key_create() fails and returns the corresponding value.
Set Thread-Specific Datapthread_setspecific(3THR)Use pthread_setspecific(3THR) to set the thread-specific binding to the specified thread-specific data key.
Return Valuespthread_setspecific() returns zero after completing successfully. Any other return value indicates that an error occurred. When any of the following conditions occur, pthread_setspecific() fails and returns the corresponding value.
Note - pthread_setspecific() does not free its storage. If a new binding is set, the existing binding must be freed; otherwise, a memory leak can occur. Get Thread-Specific Datapthread_getspecific(3THR)Use pthread_getspecific(3THR) to get the calling thread's binding for key, and store it in the location pointed to by value.
Return ValuesNo errors are returned. | ||||||||
| ||||||||