From owner-freebsd-stable Fri Sep 29 6:25:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 7A51437B424 for ; Fri, 29 Sep 2000 06:25:36 -0700 (PDT) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id PAA29930; Fri, 29 Sep 2000 15:24:30 +0200 To: Daniel Eischen Subject: Re: pthreads bug? Message-ID: <970233870.39d4980e3f303@webmail.harmonic.co.il> Date: Fri, 29 Sep 2000 15:24:30 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@freebsd.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Daniel Eischen : > > > 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