Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pthread_exit(3t) [hpux man page]

pthread_exit(3T)														  pthread_exit(3T)

NAME
pthread_exit() - cause the calling thread to terminate SYNOPSIS
PARAMETERS
value_ptr The calling thread's exit status. DESCRIPTION
terminates the calling thread. The calling thread returns an exit status in value_ptr. This value is returned to a joining thread calling on the terminating thread. Only threads created with the detachstate attribute value can return an exit status to The exit status of a detached thread is lost when the thread terminates. When a thread terminates, process-shared resources are not released. Examples of process-shared resources include mutexes, condition vari- ables, semaphores, message queue descriptors, and file descriptors. The routines are not called when a thread terminates as this is a process termination action. An implicit call to is made when a thread returns from its start routine. The function's return value serves as the thread's exit status (see pthread_create(3T)). If the main thread returns from without calling the process will exit using the return value from as the exit status. If the main thread calls the process will continue executing until the last thread terminates or a thread calls After the last thread in the process terminates, the process will exit with an exit status of zero. Any installed cancellation cleanup handlers will be popped and executed in the reverse order that they were installed. After the cancella- tion cleanup handlers have been executed, if the thread has any non-NULL thread-specific data values with associated destructor functions, the destructor functions are called. The order in which these destructor functions are called is unspecified. Calling from a cancellation cleanup handler or destructor function that was invoked because of thread termination results in undefined behavior. After a thread has terminated, the result of access to local (auto) variables of the thread is undefined. The terminating thread should not use local variables for the value_ptr parameter value. RETURN VALUE
None. ERRORS
None, this function does not return. AUTHOR
was derived from the IEEE POSIX P1003.1c standard. SEE ALSO
pthread_create(3T), pthread_join(3T), exit(2), wait(2). STANDARDS CONFORMANCE
Pthread Library pthread_exit(3T)

Check Out this Related 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)
Man Page

Featured Tech Videos