Date: Thu, 6 Oct 2005 22:30:24 GMT From: Daniel Eischen <deischen@freebsd.org> To: freebsd-threads@FreeBSD.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Message-ID: <200510062230.j96MUOpG040607@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR threads/84778; it has been noted by GNATS. From: Daniel Eischen <deischen@freebsd.org> To: freebsd@spatula.net Cc: bug-followup@freebsd.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Date: Thu, 6 Oct 2005 18:25:56 -0400 (EDT) On Thu, 6 Oct 2005 freebsd@spatula.net wrote: > What about them is "not possible" exactly? Because [_]nanosleep() does not call pthread_setconcurrency(). And pthread_setconcurrency() does not call pthread_mutexattr_init(). > What about ktrace showing a tight loop of kse_release calls followed by > RET kse_release 0? > > Why is it perfectly fine with libc_r? Libc_r is a totally different beast. You can't necessarily compare apples and oranges. There are much more likely to be race conditions exposed using libpthread than with libc_r. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510062230.j96MUOpG040607>