Date: Fri, 2 Oct 2009 15:57:30 -0700 From: Justin Teller <justin.teller@gmail.com> To: Jilles Tjoelker <jilles@stack.nl> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: Signals and an exiting thread Message-ID: <c47019cc0910021557x79c31851g91556c6d3b6f753@mail.gmail.com> In-Reply-To: <20091002223147.GA26556@stack.nl> References: <c47019cc0909301102y189a0b8aq47d23efae549f4ab@mail.gmail.com> <20091001120730.GR3130@deviant.kiev.zoral.com.ua> <20091002201213.GA16633@stack.nl> <c47019cc0910021508h1119e6f4ha9a27f4bfd071da2@mail.gmail.com> <20091002223147.GA26556@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 2, 2009 at 3:31 PM, Jilles Tjoelker <jilles@stack.nl> wrote: > On Fri, Oct 02, 2009 at 03:08:17PM -0700, Justin Teller wrote: >> However, we did a little more investigation, and the SIGKILL example >> Jilles posted happens as well. =A0We post a SIGKILL to a thread, and the >> thread goes away before it can kill the process. > > If you mean pthread_kill() with "posting to a thread", then that does > not seem a bug. I expect that pthread_kill() signals are lost when a > thread exits and that pthread_kill() to a thread that has already > terminated but has not yet been joined does nothing (possibly returning > an error). > > If a SIGKILL from kill() is lost, that is a bug. > > -- > Jilles Tjoelker > It is a SIGKILL from kill(). I'll look at code and see if I can come up with a good patch to fix it. -Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c47019cc0910021557x79c31851g91556c6d3b6f753>