Lines Matching full:signals
144 The trouble with using signals to suspend threads is that it means a thread
198 There are (at least) two ways to handle the incoming signals:
200 (a) Always accept signals. If we're in a critical section, the signal
204 (b) Block signals in critical sections. This ensures that we can't be
209 Because UNIX signals are unreliable (you can only know that you have been
212 of pthread_sigmask() and the desire to actually block signals. Either way,
214 having two (i.e. block signals and set a flag, then only send a signal
221 Some other concerns with flinging signals around:
1498 * o child thread wakes, signals condition var to wake parent
3618 * Send the signals, separated by a brief interval to allow debuggerd
3630 * The target thread can continue to execute between the two signals.