Per Jessen wrote:
Uh, how do know you it's do with the version-number?? Did I miss that
posting?
Not necessarily to do with the version number itself - it's that PHP is
dying before having actually done anything - it never gets to any PHP code.
From the first post - the last line of what I pasted below:
php -v:
PHP 5.2.3 with Suhosin-Patch 0.9.6.2 (cli) (built: Sep 12 2007 08:59:52)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
Segmentation fault (core dumped)
In my experience, the Suhosin patch (while excellent for security)
caused significant instability in several modules. I ended up having to
scrap it. (It may not have been the patch - it could easily have been
several of the PECL modules we were using. Regardless, they didn't
segfault without the Suhosin patch.)
If possible, you could try building without the patch.
Assuming your machine isn't overclocked and has been tested for hardware
problems...
If the version of PHP you're using is a binary package, you should
probably generate a backtrace from the core that was dumped and report
it as a bug to the provider of that binary. The same goes if it was
built as a FreeBSD port - they should probably know that their default
port builds are segfaulting.
I think Stut's advice for troubleshooting is a good path to take as well.
jon
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
