Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jan 2008 18:13:41 -0500
From:      Jim Pingle <lists@pingle.org>
To:        "Chris H." <chris#@1command.com>
Cc:        freebsd-stable@freebsd.org, freebsd-ports@freebsd.org
Subject:   Re: /usr/bin/objformat is missing
Message-ID:  <479FB325.2050502@pingle.org>
In-Reply-To: <20080129132449.v2c30ktam8gsc04o@webmail.1command.com>
References:  <20080128093349.ok9nt1obkkcwgco8@webmail.1command.com>	<20080128201148.GA70603@eos.sc1.parodius.com>	<20080128125242.49nlnjqf8gowkckw@webmail.1command.com>	<Pine.GSO.4.64.0801281600220.7738@sea.ntplx.net>	<20080128135210.3v6o66baugo88s44@webmail.1command.com>	<20080128144156.d1earbfa8gk0k40o@webmail.1command.com>	<20080129082918.GO48382@server.vk2pj.dyndns.org>	<20080129013719.hqwqye20go8sgocw@webmail.1command.com>	<a31046fc0801290249v25ae2660g648d972a29145382@mail.gmail.com>	<20080129074959.d1nwgk9bsw08400s@webmail.1command.com> <20080129132449.v2c30ktam8gsc04o@webmail.1command.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Chris H. wrote:
[snip]
> While it
> didn't fix my seeming php5 module number limitation. I was able, after
> trial and error, to discover that the recode module was the module
> causing Apache to dump core. Simply removing it from the list cured
> it. :) Further investigation reveals that there are some issues with
> with recode versions greater than 3.5. PHP recommends using 3.5. But,
> as I already use iconv, and mbstring, using recode is kind of overkill
> anyway. So forget it. :)
[snip]

I've had my fair share of trouble regarding PHP4 and PHP5 crashing Apache 
with certain extensions, as documented here:

http://www.pingle.org/2006/10/18/php-crashes-extensions/

Here:
http://www.pingle.org/2007/05/13/php-crashes-extensions-2/

and here:
http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround/

It happens with PHP4, PHP5, Apache 1.x and Apache 2.x.

My workaround is a hackish script that reorders the problematic extensions 
to the end of extension.ini, and in a specific order. It Works For Me, but 
YMMV. I'm glad you were able to get around the problem by simply disabling 
an extension, but some of us aren't so lucky :)

Jim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479FB325.2050502>