From owner-freebsd-questions@FreeBSD.ORG Mon May 9 15:31:10 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 024921065674 for ; Mon, 9 May 2011 15:31:10 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtp.3dresearch.com (dorabella.3dresearch.com [66.167.251.2]) by mx1.freebsd.org (Postfix) with ESMTP id ABFC18FC1A for ; Mon, 9 May 2011 15:31:09 +0000 (UTC) Received: from fracasso.3dresearch.com (pool-96-236-232-63.pitbpa.east.verizon.net [96.236.232.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vmail.3dresearch.com (Postfix) with ESMTP id 014A92E329; Mon, 9 May 2011 11:31:09 -0400 (EDT) Received: from fracasso.3dresearch.com (localhost [127.0.0.1]) by fracasso.3dresearch.com (Postfix) with SMTP id 7AE625CAC; Mon, 9 May 2011 11:31:07 -0400 (EDT) Date: Mon, 9 May 2011 11:30:30 -0400 From: Janos Dohanics To: Michael Powell Message-Id: <20110509113030.3d967a25.web@3dresearch.com> In-Reply-To: References: <20110506093157.4b34ce22.web@3dresearch.com> <87zkmzjyfe.wl%h.skuhra@gmail.com> <20110508140044.77e4137c.web@3dresearch.com> <20110509030247.9c7945cb.web@3dresearch.com> X-Mailer: Sylpheed 3.1.0 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: firefox-4.0.1,1 crashes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 15:31:10 -0000 On Mon, 09 May 2011 03:37:28 -0400 Michael Powell wrote: > Janos Dohanics wrote: > > [snip] > >> > > >> > And it's not a requirement. I've never seen that issue, or > >> > enabled the fix although firefox is my primary browser. > >> > >> These options are present in the GENERIC kernel and you probably > >> did not remove them. My guess is the OP did and never realized it. > >> At least that's how it is in Release, if Stable is different I > >> wouldn't know. > [snip] > > > > Actually, I build custom kernels, and I must have deleted the option > > P1003_1B_SEMAPHORES by accident. > > Yes. Been there done that myself. Before Firefox 4 it didn't matter. > > > FreeBSD 7.3-RELEASE Release Notes says that "FreeBSD now supports > > POSIX semaphores (P1003_1B_SEMAPHORES kernel option) by default" - > > I should assume then that the option P1003_1B_SEMAPHORES has been > > included by default in all 8.x versions, correct? > > > > Yes. A snip from GENERIC: > > options SYSVSHM # SYSV-style shared > memory options SYSVMSG # SYSV-style > message queues options SYSVSEM # > SYSV-style semaphores options P1003_1B_SEMAPHORES # > POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # > POSIX P1003_1B real-time extensions > > Whenever a userland app gives problems it's very easy to fixate on > the app being broken, and most of the time that is indeed the case. > When it's complaining about some kind of support library or function > missing, or throwing an error, the next thing to look for is the > source for the error in whatever upstream dependency. In this > particular case the location of the complaint just happened to be > something which is in the default kernel. This is why I knew you had > built a custom kernel and removed this. Like I said, been there done > that. > > -Mike Thanks for your help - so many ways to mess up... :) -- Janos Dohanics