PTHREAD_KILL(3) Linux Programmer's Manual PTHREAD_KILL(3)NAME
pthread_kill - send a signal to a thread
SYNOPSIS
#include <signal.h>
int pthread_kill(pthread_t thread, int sig);
Compile and link with -pthread.
DESCRIPTION
The pthread_kill() function sends the signal sig to thread, a thread in the same process as the caller. The signal is asynchronously
directed to thread.
If sig is 0, then no signal is sent, but error checking is still performed; this can be used to check for the existence of a thread ID.
RETURN VALUE
On success, pthread_kill() returns 0; on error, it returns an error number, and no signal is sent.
ERRORS
EINVAL An invalid signal was specified.
ESRCH No thread with the ID thread could be found.
CONFORMING TO
POSIX.1-2001.
NOTES
Signal dispositions are process-wide: if a signal handler is installed, the handler will be invoked in the thread thread, but if the dispo-
sition of the signal is "stop", "continue", or "terminate", this action will affect the whole process.
SEE ALSO kill(2), sigaction(2), sigpending(2), pthread_self(3), pthread_sigmask(3), raise(3), pthreads(7), signal(7)COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2012-08-19 PTHREAD_KILL(3)
Check Out this Related Man Page
PTHREAD_KILL(3) Linux Programmer's Manual PTHREAD_KILL(3)NAME
pthread_kill - send a signal to a thread
SYNOPSIS
#include <signal.h>
int pthread_kill(pthread_t thread, int sig);
Compile and link with -pthread.
DESCRIPTION
The pthread_kill() function sends the signal sig to thread, another thread in the same process as the caller. The signal is asynchronously
directed to thread.
If sig is 0, then no signal is sent, but error checking is still performed; this can be used to check for the existence of a thread ID.
RETURN VALUE
On success, pthread_kill() returns 0; on error, it returns an error number, and no signal is sent.
ERRORS
ESRCH No thread with the ID thread could be found.
EINVAL An invalid signal was specified.
CONFORMING TO
POSIX.1-2001.
NOTES
Signal dispositions are process-wide: if a signal handler is installed, the handler will be invoked in the thread thread, but if the dispo-
sition of the signal is "stop", "continue", or "terminate", this action will affect the whole process.
SEE ALSO kill(2)sigaction(2), sigpending(2), pthread_self(3), pthread_sigmask(3), raise(3), pthreads(7), signal(7)COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2009-01-28 PTHREAD_KILL(3)
I have been toying with the idea of posting a thread asking for your dumbest mistakes so that we may all learn from each other.
"A smart man learns from his own mistakes,
A wise man learns from others' mistakes"
I think I will start us off. I haven't had too many that were really bad, but... (6 Replies)
Hi folks
I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file.
The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
hi all,
i had created 3 threads using pthreads. Each thread does a different job. Now the main problem is when one thread generates a signal (for example SIGFPE, SIGINT) then the process terminates and all other threads do terminate eventually.
I want to keep other threads running i.e, i... (0 Replies)
Is it possible to send a custom signal to a process?
e.g. Send signal 9999 to my process, which handles it with some custom handler.
How would one do this? (12 Replies)
In this post at 302451613-post2.html the link to the code comes up not found. The thread is closed, so I was unable to ask on the thread itself and I do not have enough posts yet to send a private message (or write out a proper html link). Does the author (jim mcanamara) have an updated link?
... (2 Replies)