From owner-freebsd-current@FreeBSD.ORG Tue Mar 23 07:01:57 2004 Return-Path: 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 7D3AF16A4D4; Tue, 23 Mar 2004 07:01:57 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16ADB43D2D; Tue, 23 Mar 2004 07:01:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i2NF1svK019078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Mar 2004 10:01:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i2NF1hwP019699; Tue, 23 Mar 2004 10:01:43 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16480.20823.548119.582640@grasshopper.cs.duke.edu> Date: Tue, 23 Mar 2004 10:01:43 -0500 (EST) To: Joe Marcus Clarke In-Reply-To: <1080050628.777.2.camel@gyros> References: <16479.30826.56912.226587@knock.econ.vt.edu> <20040322180728.F5352@carver.gumbysoft.com> <20040323121441.1e535e57@Magellan.Leidinger.net> <1080050628.777.2.camel@gyros> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: FreeBSD GNOME Users cc: Alexander Leidinger cc: freebsd-current@FreeBSD.org cc: "Russell D. Murphy Jr." Subject: Re: Mozilla crash and burn? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 23 Mar 2004 15:01:57 -0000 Joe Marcus Clarke writes: > > Feel free to make suggestions. I keep the work directory of the port in > > case someone has a clever idea what to try next... > > Me, either. Mozilla works just fine for me. I've never seen any of the > crashes you describe. The URLs you mentioned above work fine for me (I > go to GnomeDesktop a lot). I'm running -CURRENT from yesterday with all > debugging disabled. Perhaps this is something triggered by WITNESS... > WITNESS is is confined to the kernel, the only affect it could have on a user binary would be to slow it down ;) Since the problems involve threads and locking, is there any chance that the people with problems are running mixed libc_r and libpthread (aka KSE) binaries? Has anybody tried globally mapping libc_r to libpthread as suggested in the 20040303 entry of src/UPDATING? Drew