From owner-freebsd-current  Sun Jan  5  7: 0:18 2003
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A8CCD37B401; Sun,  5 Jan 2003 07:00:16 -0800 (PST)
Received: from sweb.uky.edu (sweb.uky.edu [128.163.2.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0B3CC43EC2; Sun,  5 Jan 2003 07:00:16 -0800 (PST)
	(envelope-from david@uky.edu)
Received: from uky.edu (198-93-125-90.extended.qx.net [198.93.125.90])
	(authenticated bits=0)
	by sweb.uky.edu (8.12.3/8.12.3) with ESMTP id h05EqUEC016270
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Sun, 5 Jan 2003 09:52:34 -0500 (EST)
	(envelope-from david@uky.edu)
Date: Sat, 4 Jan 2003 21:57:34 -0500
Subject: Re: pthread ^T problem on recent -CURRENT: death in libc_r mutex
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: Juli Mallett <jmallett@FreeBSD.org>, current@FreeBSD.org
To: Robert Watson <rwatson@FreeBSD.org>
From: David Rhodus <david@uky.edu>
In-Reply-To: <Pine.NEB.3.96L.1030104175853.82416D-100000@fledge.watson.org>
Message-Id: <7076C6DC-2059-11D7-94F8-00039380DD2C@uky.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


On Saturday, January 4, 2003, at 06:00 PM, Robert Watson wrote:

>
> On Sat, 4 Jan 2003, Juli Mallett wrote:
>
>> * De: Robert Watson <rwatson@FreeBSD.org> [ Data: 2003-01-04 ]
>> 	[ Subjecte: pthread ^T problem on recent -CURRENT: death in libc_r 
>> mutex ]
>>>
>>> Juli Mallett pointed me at the following reproduceable problem on my
>>> -current notebook with userland/kernel dated Dec 29:
>>
>> Incidentally, this doesn't illustrate the problem I was actually 
>> trying
>> to point out.  Try making the sleep's pthread_yield().  That will make
>> the threads never run again.  sleep is the hack I've had to do.  In my
>> appp, I have a 'my_yield' function which will sleep on FreeBSD, and
>> yield on everywhere else :(
>
> Hmm.  I'm not experiencing that problem -- if I replace the sleep() 
> with
> pthread_yield(), I get a long sequence of '1's until thread2 is 
> started,
> and then clean alternation between '1' and '2'.  I don't see any 
> failure
> to schedule a thread after it has yielded.
>
> I'm updating my box from Dec 29 to today to see if that makes a 
> difference
> either way on either problem.
>
With pthread_yield() I get the same as Watson. It still core's with a 
few ctrl-T's.
I'm running today's source.

-DR


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message