From owner-freebsd-current Sat Jan 4 15: 0:34 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 7253837B401; Sat, 4 Jan 2003 15:00:33 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDF1743E4A; Sat, 4 Jan 2003 15:00:32 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id h04N0W1Z084585; Sat, 4 Jan 2003 18:00:32 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 4 Jan 2003 18:00:32 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Juli Mallett Cc: current@FreeBSD.org Subject: Re: pthread ^T problem on recent -CURRENT: death in libc_r mutex In-Reply-To: <20030104142844.A65065@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 4 Jan 2003, Juli Mallett wrote: > * De: Robert Watson [ 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. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message