From owner-freebsd-current@FreeBSD.ORG Tue Sep 5 04:08:48 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 F2ED016A4E0 for ; Tue, 5 Sep 2006 04:08:47 +0000 (UTC) (envelope-from harikurniawan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11A0643D7F for ; Tue, 5 Sep 2006 04:08:37 +0000 (GMT) (envelope-from harikurniawan@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so1331791nfc for ; Mon, 04 Sep 2006 21:08:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=MHIRpEMe65boVSV41FonBKwzZxGl1Knlao7qDYT0j3mrJZWWkB2qyZ1YnDop+Qpm5wo16lZZAaimupVyD+sMFoaLc/ZyQWMVzwia3aEgIBr7j/+H/dpAmzqF34YLZhmxKZm1tUAjfMnDTN9ie1r5SYZgFQZ94h28vXM3Phqp188= Received: by 10.48.254.10 with SMTP id b10mr7325681nfi; Mon, 04 Sep 2006 21:08:36 -0700 (PDT) Received: by 10.49.18.11 with HTTP; Mon, 4 Sep 2006 21:08:36 -0700 (PDT) Message-ID: <4c40c4e70609042108k39cdd87ey2bf9d04d7e856c17@mail.gmail.com> Date: Tue, 5 Sep 2006 11:08:36 +0700 From: "Angka H. K." To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: libpthread error 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: Tue, 05 Sep 2006 04:08:48 -0000 A few weeks ago there is problem with libpthread that cause many unstable application, refer to this post : http://lists.freebsd.org/pipermail/freebsd-current/2006-July/064676.html I am having problem with glxgears that complaining with the same error when that bug exist. Is it just me picking th source at the wrong time or this bug is show up again ? My source synced at 3 Sept 2006, and planning this friday to resync again. Regards,