Date: Fri, 4 Jan 2008 11:12:37 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: Threads and signals Message-ID: <20080104191237.GK76698@elvis.mu.org> In-Reply-To: <fll7jv$n9v$1@ger.gmane.org> References: <fljin9$crb$1@ger.gmane.org> <20080104011821.GD76698@elvis.mu.org> <9bbcef730801040325y197aa7f6s134436dcc79d8aeb@mail.gmail.com> <20080104115927.GJ76698@elvis.mu.org> <fll7jv$n9v$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Ivan Voras <ivoras@freebsd.org> [080104 04:06] wrote: > Alfred Perlstein wrote: > > * Ivan Voras <ivoras@freebsd.org> [080104 03:23] wrote: > >> On 04/01/2008, Alfred Perlstein <alfred@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080104191237.GK76698>