From owner-freebsd-current@FreeBSD.ORG Mon Jul 17 17:12:06 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 78E6416A4DD; Mon, 17 Jul 2006 17:12:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51E4A43D7B; Mon, 17 Jul 2006 17:11:50 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6HHBlVp038882; Mon, 17 Jul 2006 13:11:49 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 17 Jul 2006 13:09:33 -0400 User-Agent: KMail/1.9.1 References: <20060716232338.2357f50a.nork@FreeBSD.org> In-Reply-To: <20060716232338.2357f50a.nork@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607171309.34139.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 17 Jul 2006 13:11:49 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1600/Sat Jul 15 11:03:46 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Norikatsu Shigemura Subject: Re: many thread applications are unstable on 7-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 17:12:06 -0000 On Sunday 16 July 2006 10:23, Norikatsu Shigemura wrote: > I think that this is FYI, maybe. Sorry, I don't know why it causes. > I could not trace problems. Does this only happen with libpthread or does it also happen with libthr? -- John Baldwin