From owner-freebsd-current@FreeBSD.ORG Tue May 20 17:01:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92AC91065675; Tue, 20 May 2008 17:01:39 +0000 (UTC) (envelope-from amoran@forsythia.net) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 78E708FC0A; Tue, 20 May 2008 17:01:39 +0000 (UTC) (envelope-from amoran@forsythia.net) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 66BCE2D8D6AB; Tue, 20 May 2008 10:01:39 -0700 (PDT) Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Mail Security) with ESMTP id 4F51A2808D; Tue, 20 May 2008 10:01:39 -0700 (PDT) X-AuditID: 11807130-acb96bb000000ead-99-483303f3e9f9 Received: from cenarius.apple.com (cenarius.apple.com [17.228.13.75]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay11.apple.com (Apple SCV relay) with ESMTP id 3461A28091; Tue, 20 May 2008 10:01:39 -0700 (PDT) Message-Id: From: Andrew Moran To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 20 May 2008 10:01:39 -0700 References: <1d3ed48c0805191759mc54c4f2r7f00b533efeac73d@mail.gmail.com> <483237A9.6030108@barryp.org> <483258E7.5090301@psg.com> X-Mailer: Apple Mail (2.919.2) X-Brightmail-Tracker: AAAAAA== Cc: Subject: Re: Updated php, and apache segfaults on SIGHUP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 May 2008 17:01:39 -0000 OK I've narrowed down my problem to: extension=mhash.so in extensions.ini If I comment out that php extension, I'm good. If I don't, I crash when sending HUP signal to parent apache process. I experimented with the order of the extensions.ini file but could not get to work regardless of putting that mhash in the beginning or the end of the file. On freebsd 7, I've cvsup'd and rebuilt all ports, so I know it's not an 'out of date' kind of thing. Hmm.. --Andy On May 20, 2008, at 8:02 AM, Sean C. Farley wrote: > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > " >