pthread_cond_signal
pthread_mutexattr_gettype
pthread_attr_destroy
pthread_attr_getstacksize
pthread_create
pthread_getspecific
pthread_attr_init
pthread_exit
pthread_attr_getstack
pthread_getcpuclockid
pthread_attr_getstackaddr
pthread_key_delete
__pthread_cleanup_pop
pthread_mutexattr_destroy
pthread_equal
pthread_attr_getguardsize
pthread_cond_timedwait_mo
pthread_detach
pthread_attr_getschedpoli
pthread_attr_setstackaddr
pthread_getschedparam
pthread_cond_broadcast
pthread_once
pthread_setschedparam
pthread_key_create
pthread_kill
pthread_cond_timeout_np
pthread_getattr_np
pthread_attr_setstacksize
pthread_sigmask
pthread_cond_init
__pthread_cleanup_push
pthread_attr_setstack
pthread_mutexattr_settype
pthread_attr_getdetachsta
pthread_mutex_unlock
pthread_self
pthread_mutexattr_init
__pthread_clone
pthread_mutex_destroy
pthread_mutex_lock
pthread_cond_wait
pthread_attr_setguardsize
pthread_mutex_trylock
pthread_cond_destroy
pthread_attr_setschedpoli
pthread_mutex_init
pthread_attr_setschedpara
pthread_attr_setdetachsta
pthread_join
pthread_cond_timedwait
pthread_attr_getschedpara
pthread_setspecific
end of line.
2008/12/23 mak <mayank....@gmail.com>:
Another more rustic alternative is to either close/shutdown the file
descriptor or resource the thread is waiting on, or even use
pthread-kill to send a signal to the thread, since this sill make the
system call return with EINTR (you need to unblock the signal first
though)
In all cases, be sure to properly release resources when exiting thr
thread. 99% of the code that uses pthread_cancel I have seen leaks
memory, or even locks, in certain circumstances.