From owner-freebsd-stable@FreeBSD.ORG Wed Aug 13 13:33:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD2E71065676; Wed, 13 Aug 2008 13:33:40 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 106388FC0C; Wed, 13 Aug 2008 13:33:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48A2E2AD.8060607@FreeBSD.org> Date: Wed, 13 Aug 2008 15:33:33 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Borja Marcos References: <43EC06E9-76B3-4AA1-BC5E-4E1BD64AFC2D@SARENET.ES> <0296197A-28ED-4DAA-A31F-C28471E864FB@SARENET.ES> <20080812102856.GA6735@eos.sc1.parodius.com> <659A017B-5D6F-4B74-A85D-4A9A040CA442@SARENET.ES> <48A2DF31.4050907@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , freebsd-stable@freebsd.org, Ivan Voras Subject: Re: umtxn and Apache 2.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2008 13:33:40 -0000 Borja Marcos wrote: > > On Aug 13, 2008, at 3:18 PM, Kris Kennaway wrote: > >> Borja Marcos wrote: >>> ((Sorry for the long dump)) >>> (gdb) bt >>> #0 0x3827cfe7 in __error () from /lib/libthr.so.3 >>> #1 0x3827cd4a in __error () from /lib/libthr.so.3 >>> #2 0x08702120 in ?? () >> >> As you can see the debugging symbols are still not available. Refer >> to the developers handbook if you need more assistance doing this. > > Hmm. Weird. I compiled the port having WITH_DEBUG defined (as I saw in > the Makefile) and indeed the gcc invocations has the -g flag set. What > is strange is the error gdb issued, offering a coredump, etc. It is likely that the binaries are stripped on install then. You can try to run gdb against the compiled versions in the port work/ directory. >> Also, it is worth carefully checking your php configuration. For >> example, php is notoriously sensitive to the order in which modules >> are defined, and will crash or misbehave without giving any other >> warnings if you don't meet its expectations. That may or may not be >> relevant in your situation. > > Just in case I didn't change the order of the modules. I'll keep looking > at it. This could be why :) Some people report that previously working configurations stopped working after an upgrade until the ordering was changed. Kris