Date: Fri, 29 Oct 2004 14:51:59 +1000 From: John Birrell <jb@cimlogic.com.au> To: David Xu <davidxu@freebsd.org> Cc: threads@freebsd.org Subject: Re: Infinite loop bug in libc_r on 4.x with condition variables and signals Message-ID: <20041029045159.GG47792@freebsd3.cimlogic.com.au> In-Reply-To: <41818397.8090303@freebsd.org> References: <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net> <200410281554.07222.jhb@FreeBSD.org> <20041028203900.GF47792@freebsd3.cimlogic.com.au> <41818397.8090303@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 2004 at 07:41:11AM +0800, David Xu wrote: > It would be nice if you could provide some example code, even if the code > may contains bug, it is still good for me to see how pthread_cancel can > cause SIG 11, because pthread_cancel seems checking everything carefully. (Note that it is pthread_testcancel, not pthread_cancel, and it is libpthread makeing the call, not the application directly) Sorry, there is absolutely no way I can get a simple/example program. The application only does it when it is loaded serving data at about 4 Mb/s. I haven't seen the SIG 11 on any of my test systems and I *have* tried to create test loads. It only happens on the production server serving the real world. 8-( A second instance of the same program, running on the same server, serving a different group of users at a lower bit rate has never had the problem. -- John Birrell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041029045159.GG47792>