Date: Thu, 31 Jan 2008 11:36:48 -0800 From: Landon Fuller <landonf@bikemonkey.org> To: Julian Elischer <julian@elischer.org> Cc: Daniel Eischen <deischen@freebsd.org>, Gary Stanley <gary@velocity-servers.net>, Robert Watson <rwatson@FreeBSD.org>, freebsd-threads@freebsd.org Subject: Re: threads/119920: fork broken in libpthread Message-ID: <6DCF8C56-DFF9-41CB-8AC9-E7EB9F9A1CCC@bikemonkey.org> In-Reply-To: <47A22220.70006@elischer.org> References: <200801240850.m0O8o2JQ023500@freefall.freebsd.org> <4798564B.7070500@elischer.org> <Pine.GSO.4.64.0801240957550.16059@sea.ntplx.net> <20080128185830.B56811@fledge.watson.org> <479E3079.3000803@elischer.org> <20080129222455.T53151@fledge.watson.org> <20080131093321.K35034@fledge.watson.org> <47A2170D.6020308@elischer.org> <42D09215-18FD-43A1-97E8-D4CC9E97AFDD@bikemonkey.org> <47A22097.2040303@elischer.org> <79EBC63D-72A1-4CB9-962C-C4649544FF7A@bikemonkey.org> <47A22220.70006@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Jan 31, 2008, at 11:31, Julian Elischer wrote: > Landon Fuller wrote: >> The children processes spin (in either sigprocmask() or >> _lockuser_reinit()), and the parent process thread wedges on >> waitpid(). > > so if the children show up in top at all (usually they are already > exited by the time top looks) then the problem has been hit. right? Exactly. With the test case's default number of threads, one should see up to four children appear in top, eating CPU. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHoiNQlplZCE/15mMRAojqAJ9q5PAVEmuVlHzWbxcB1RNK5MMCGwCfVenx bYRpn5bUNyS2BMkISDpEOfc= =ttJe -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6DCF8C56-DFF9-41CB-8AC9-E7EB9F9A1CCC>