Date: Fri, 4 Jan 2008 11:58:54 -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: <20080104195854.GL76698@elvis.mu.org> In-Reply-To: <9bbcef730801041139o4a54c069t772ab28aea7d3900@mail.gmail.com> 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> <20080104191237.GK76698@elvis.mu.org> <9bbcef730801041139o4a54c069t772ab28aea7d3900@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Ivan Voras <ivoras@freebsd.org> [080104 11:37] wrote: > On 04/01/2008, Alfred Perlstein <alfred@freebsd.org> wrote: > > > You need to read up on signals, look at sigaction, pthread_sigmask, > > sigprocmask and such. > > Yes I do :) > > I missed pthread_sigmask because pthread(3) doesn't mention it. It's > much clearer now that I know it exists. One more thing. I apologize if I came across too sternly or impatient, while I know the general way to do this, it's not fresh in my mind and I'm kind of busy. :) thank you, -- - Alfred Perlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080104195854.GL76698>