From owner-freebsd-questions@FreeBSD.ORG Mon May 9 07:33:28 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 569E3106566B for ; Mon, 9 May 2011 07:33:28 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id D77E78FC13 for ; Mon, 9 May 2011 07:33:27 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QJKy5-0001Yq-PF for freebsd-questions@freebsd.org; Mon, 09 May 2011 09:33:25 +0200 Received: from pool-173-79-85-36.washdc.fios.verizon.net ([173.79.85.36]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 May 2011 09:33:25 +0200 Received: from nightrecon by pool-173-79-85-36.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 May 2011 09:33:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Mon, 09 May 2011 03:37:28 -0400 Lines: 43 Message-ID: References: <20110506093157.4b34ce22.web@3dresearch.com> <87zkmzjyfe.wl%h.skuhra@gmail.com> <20110508140044.77e4137c.web@3dresearch.com> <20110509030247.9c7945cb.web@3dresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: pool-173-79-85-36.washdc.fios.verizon.net 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 07:33:28 -0000 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