Threads and signals

Alfred Perlstein alfred at freebsd.org
Fri Jan 4 11:15:06 PST 2008


* Ivan Voras <ivoras at freebsd.org> [080104 04:06] wrote:
> Alfred Perlstein wrote:
> > * Ivan Voras <ivoras at freebsd.org> [080104 03:23] wrote:
> >> On 04/01/2008, Alfred Perlstein <alfred at freebsd.org> wrote:
> >>
> >>> You need to block/unblock signals or use sigwait.
> >>>
> >>> So basically your code will look something like:
> >>>   defer_signals();
> >> Interesting approach - should I also use it to ensure only one of the
> >> threads gets the signal?
> > 
> > Certainly.
> 
> Hmm:
> 
> :/usr/include> man defer_signals
> No manual entry for defer_signals
> :/usr/include> grep -r defer_signals *
> -nothing found
> 
> Where is defer_signals() ?
> 

That was psuedocode.

You need to read up on signals, look at sigaction, pthread_sigmask,
sigprocmask and such.

-- 
- Alfred Perlstein


More information about the freebsd-threads mailing list