Signals and an exiting thread
Andriy Gapon
avg at icyb.net.ua
Thu Oct 1 12:53:38 UTC 2009
on 30/09/2009 21:02 Justin Teller said the following:
> We're trying to control one process from another process through
> signals (I know, revolutionary ;-), and we've found that a signal
> occasionally gets lost. The process we're signaling is
> multi-threaded. It looks like the signal is lost when the kernel
> decides to post the signal to a thread that is in the process of dying
> (calling pthread_exit, etc).
>
> Is this expected behavior that we should just handle, or is it a race
> in the kernel that should be/will be/already is fixed?
>
> It may be that a fix is already in current, and I just haven't found
> it in my searches through the source code (I'm working off of source
> code for an older 8.0 image). If it is fixed, I'd appreciate a
> pointer to the code that fixes it.
>
> Thanks in advance for the help
Do you allow all/arbitrary threads to catch signals?
not sure if the following applies to your case, but for multi-threaded
applications we usually designate a dedicated signal handling thread.
sigwait(2), pthread_sigmask(2), etc
--
Andriy Gapon
More information about the freebsd-current
mailing list