thr_exit man page on SmartOS

Man page or keyword search:  
man Server   16655 pages
apropos Keyword Search (all sections)
Output format
SmartOS logo
[printable version]

THR_EXIT(3C)							  THR_EXIT(3C)

       thr_exit - terminate the calling thread

       cc -mt [ flag... ] file...[ library... ]
       #include <thread.h>

       void thr_exit(void *status);

       The thr_exit() function terminates the calling thread, in a similar way
       that exit(3C) terminates the calling process. If the calling thread  is
       not  detached,  then  the  thread's ID and the exit status specified by
       status are retained. The value status is then  made  available  to  any
       successful  join with the terminating thread (see thr_join(3C)); other‐
       wise, status is disregarded allowing the thread's ID  to	 be  reclaimed

       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,  appropriate  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, call‐
       ing any atexit() routines that might exist.

       An exiting thread runs with all signals blocked. All thread termination
       functions, including cancellation cleanup handlers and  thread-specific
       data destructor functions, are called with all signals blocked.

       If  any	thread,	 including  the	 main() thread, calls thr_exit(), only
       that thread will exit.

       If main() returns or exits (either implicitly or	 explicitly),  or  any
       thread explicitly calls exit(), the entire process will exit.

       The  behavior  of thr_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 thr_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 thr_exit() sta‐
       tus parameter value.

       If any thread (except  the  main()  thread)  implicitly	or  explicitly
       returns,	 the result is the same as if the thread called thr_exit() and
       it will return the value of status as the exit code.

       The process will terminate with an exit status of 0 after the last non-
       daemon thread has terminated (including the main() thread). This behav‐
       ior is the same as if the application had called exit() with a 0	 argu‐
       ment at thread termination time.

       The  thr_exit() function cannot return to its caller.

       No errors are defined.

       See attributes(5) for descriptions of the following attributes:

       │MT-Level       │ MT-Safe	 │

       exit(3C),      thr_create(3C),	  thr_join(3C),	    thr_keycreate(3C),
       attributes(5), standards(5)

       Although only POSIX implements cancellation, cancellation can  be  used
       with Solaris threads, due to their interoperability.

       The  status  argument  should  not reference any variables local to the
       calling thread.

				  Nov 2, 2007			  THR_EXIT(3C)

List of man pages available for SmartOS

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net