From owner-freebsd-questions@FreeBSD.ORG Tue May 20 15:22:09 2008 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 7315D1065672; Tue, 20 May 2008 15:22:09 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 351DD8FC14; Tue, 20 May 2008 15:22:08 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m4KF20Cw024223; Tue, 20 May 2008 10:02:00 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Tue, 20 May 2008 10:02:00 -0500 (CDT) From: "Sean C. Farley" To: Randy Bush In-Reply-To: <483258E7.5090301@psg.com> Message-ID: References: <1d3ed48c0805191759mc54c4f2r7f00b533efeac73d@mail.gmail.com> <483237A9.6030108@barryp.org> <483258E7.5090301@psg.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail.farley.org Cc: freebsd-current@FreeBSD.org, delphij@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: Updated php, and apache segfaults on SIGHUP 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: Tue, 20 May 2008 15:22:09 -0000 On Mon, 19 May 2008, Randy Bush wrote: > 386 very current > > i have been unable to get apache not to segv on one server for a while > now. > > i tried the php rebuild > > i tried clearing obj, full system build, full ports force rebuild, ... > > i just tried > >> If you have a backup of php/extensions.ini from before you did your >> updates, it would be worth trying reverting to that, to get the order >> you had before that seemed OK. > > still coring > > but it is nice to know i have company :) I recall mention on an E-mail list or on IRC of a core dump with PHP due to improper use of putenv(), but I do not remember where. Bug #44836[1] discusses it. It seems the patch was reverted, but I see that it is included as a patch within the ports tree. You could try to see if things improve by using the older patch[2] for FreeBSD 7 (and above) systems. Cc'ing delphij to mention that the patch was reverted in the PHP tree. Was the patch written for FreeBSD 6? I noticed that it frees memory just after the call to putenv(). The is valid for FreeBSD 6 where the string was duped, but in 7, it follows the POSIX standard of using the string directly. Sean 1. http://bugs.php.net/bug.php?id=44836 2. http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php5/files/patch-ext_standard_basic_functions.c?rev=1.1;content-type=text%2Fplain -- scf@FreeBSD.org