Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pthread_exit(3c) [sunos man page]

pthread_exit(3C)														  pthread_exit(3C)

NAME
pthread_exit - terminate calling thread SYNOPSIS
cc -mt [ flag... ] file... -lpthread [ library... ] #include <pthread.h> void pthread_exit(void *value_ptr); The pthread_exit() function terminates the calling thread, in a similar way that exit(3C) terminates the calling process. If the thread is not detached, the exit status specified by value_ptr is made available to any successful join with the terminating thread. See pthread_join(3C). Any cancellation cleanup handlers that have been pushed and not yet popped are popped in the reverse order that they were pushed and then executed. After all cancellation cleanup handlers have been executed, if the thread has any thread-specific data, appropri- ate destructor functions will be called in an unspecified order. Thread termination does not release any application visible process resources, including, but not limited to, mutexes and file descriptors, nor does it perform any process level cleanup actions, including, but not limited to, calling any atexit() routines that might exist. An implicit call to pthread_exit() is made when a thread other than the thread in which main() was first invoked returns from the start routine that was used to create it. The function's return value serves as the thread's exit status. The behavior of pthread_exit() is undefined if called from a cancellation cleanup handler or destructor function that was invoked as a result of either an implicit or explicit call to pthread_exit(). After a thread has terminated, the result of access to local (auto) variables of the thread is undefined. Thus, references to local vari- ables of the exiting thread should not be used for the pthread_exit() value_ptr parameter value. The process exits with an exit status of 0 after the last thread has been terminated. The behavior is as if the implementation called exit() with a 0 argument at thread termination time. The pthread_exit() function cannot return to its caller. No errors are defined. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ exit(3C), pthread_cancel(3C), pthread_create(3C), pthread_join(3C), pthread_key_create(3C), attributes(5), standards(5) 23 Mar 2005 pthread_exit(3C)

Check Out this Related Man Page

pthread_exit(3) 					     Library Functions Manual						   pthread_exit(3)

NAME
pthread_exit - Terminates the calling thread. LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so) SYNOPSIS
#include <pthread.h> void pthread_exit( void *value_ptr); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: IEEE Std 1003.1c-1995, POSIX System Application Program Interface PARAMETERS
Value copied and returned to the caller of pthread_join(3). Note that void * is used as a universal datatype, not as a pointer. DEC- threads treats the value_ptr as a value and stores it to be returned by pthread_join(3). DESCRIPTION
This routine terminates the calling thread and makes a status value (value_ptr) available to any thread that calls pthread_join(3) and specifies the terminating thread. Any cleanup handlers that have been pushed and not yet popped from the stack, are popped in the reverse order that they were pushed and then executed. After all cleanup handlers have been executed, appropriate destructor functions shall be called in an unspecified order if the thread has any thread-specific data. Thread termination does not release any application-visible process resources, including, but not limited to mutexes and file descriptors, nor does it perform any process-level cleanup actions, including, but not limited to calling any atexit routine that may exist. An implicit call to pthread_exit(3) is issued when a thread returns from the start routine that was used to create it. DECthreads writes the function's return value as the return value in the thread's thread object. The process exits when the last running thread calls pthread_exit(3). After a thread has terminated, the result of access to local (that is, explicitly or implicitly declared auto) variables of the thread is undefined. So, references to local variables of the existing thread should not be used for the value_ptr argument of the pthread_exit(3) routine. RETURN VALUES
None ERRORS
None RELATED INFORMATION
Functions: pthread_cancel(3), pthread_create(3), pthread_detach(3), pthread_join(3) Manuals: Guide to DECthreads and Programmer's Guide delim off pthread_exit(3)
Man Page