Date: Fri, 29 Sep 2000 15:24:30 +0200 (IST) From: Roman Shterenzon <roman@harmonic.co.il> To: Daniel Eischen <eischen@vigrid.com> Cc: freebsd-stable@freebsd.org Subject: Re: pthreads bug? Message-ID: <970233870.39d4980e3f303@webmail.harmonic.co.il> In-Reply-To: <Pine.SUN.3.91.1000929072626.7930A-100000@pcnet1.pcnet.com> References: <Pine.SUN.3.91.1000929072626.7930A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Daniel Eischen <eischen@vigrid.com>: > > > but, in fact gets blocked in the close() function. > > > Obviously it's waiting to acquire some lock. > > > Does anyone have an idea? > > > > Yes, I have an idea and an idea how to fix it, I'm wondering what > > the thread in accept() sees after this happens? > > I don't think it should be fixed unless we decide to remove the > automatic locking of file descriptors. But if you do come up > with a clean solution, please run it by me. I have some massive > changes to the threads library that are currently under review. > I'm concerned about signal delivery as well. It doesn't really work as expected. Take the small source I attached to one of my mails, add pthread_kill in the "routine" thread with parameter of "main" thread, and observe that accept() doesn't break out at all. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?970233870.39d4980e3f303>