From owner-freebsd-threads@FreeBSD.ORG Wed Jun 15 09:16:03 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A54116A41F for ; Wed, 15 Jun 2005 09:16:03 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36F2443D49; Wed, 15 Jun 2005 09:16:03 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5F9G0IB021041; Wed, 15 Jun 2005 09:16:01 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42AFF243.9080908@freebsd.org> Date: Wed, 15 Jun 2005 17:17:55 +0800 From: David Xu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mi@aldan.algebra.com, grhoten@jtcsv.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-threads@freebsd.org Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 09:16:03 -0000 Have you tried it with libthr on -CURRENT ? David Xu -----Original Message----- From: owner-freebsd-threads@freebsd.org [mailto:owner-freebsd-threads@freebsd.org]On Behalf Of Mikhail T. Sent: 2005年6月14日 10:42 To: George Rhoten; freebsd-threads@FreeBSD.org Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) = This is reproducable on the sourceforge.net NetBSD machine by executing the following: = = My initial guess is that it seems to be an OS thread scheduler bug. = The main process spins in a loop without sleeping and frequently locks = the global mutex while waiting for the other threads to finish. None = of the other threads get enough time because they are all waiting for = the global mutex lock from the main process thread when its their = turn. The main process thread is hoging the global mutex while it's in = its loop. It's not a deadlock, it's just a type of thread scheduling = that doesn't happen on other operating systems. Whether it is a bug or a legal oddity, our threads (CC-ed) people would love to hear about it... = Adding a sleep() or a yield statement in the main thread of the test = allows the test to finish. The fix will be available in ICU 3.4. -mi _______________________________________________ freebsd-threads@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-threads To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org"