PHP 4.0.5 module causes Apache child processes to segfault...

I compiled and installed PHP 4.0.5 onto our development server (Mandrake Linux 7.1 w/kernel 2.2.17) today and tried to access one of our php intensive sites on it - most of the pages wouldn't respond. This is how 4.0.5 was compiled: ./configure \ --with-apxs=/usr/local/apache_1.3.19/bin/apxs \ --with-mysql=/usr/local/mysql \ --enable-ftp \ --with-curl \ --with-zlib \ --with-pspell \ --with-ldap \ --with-pdflib \ --with-imap=/usr/local/src/imap-4.5 \ --with-zlib-dir=/usr/lib \ --with-gd \ --with-ttf \ --with-t1lib \ --with-xml \ --with-swf=/usr/local \ --with-java=/usr/local/jdk \ --with-gettext \ --with-mcrypt \ --with-mhash \ --enable-sockets \ --enable-calendar \ --enable-trans-sid \ --enable-track-vars=yes \ --enable-magic-quotes=yes Looking at the logs I saw a few of these - this wasn't happening with 4.0.4pl1: [Tue May 1 20:49:21 2001] [notice] child pid 19423 exit signal Segmentation fault (11) [Tue May 1 20:51:17 2001] [notice] caught SIGTERM, shutting down [Tue May 1 20:51:45 2001] [notice] Apache configured -- resuming normal operations [Tue May 1 20:57:41 2001] [warn] child process 19677 still did not exit, sending a SIGTERM [Tue May 1 20:57:45 2001] [error] child process 19677 still did not exit, sending a SIGKILL [Tue May 1 20:57:46 2001] [notice] caught SIGTERM, shutting down [Tue May 1 20:58:08 2001] [notice] Apache configured -- resuming normal operations [Tue May 1 20:59:11 2001] [notice] child pid 20039 exit signal Segmentation fault (11) [Tue May 1 21:00:54 2001] [notice] child pid 20290 exit signal Segmentation fault (11) I've downgraded to 4.0.4pl1 and all is well again. I've tried to generate a core dump file (Apache also has write access to a folder specified with the CoreDumpDirectory directive.) using the instructions here but have been unsuccessful: <http://www.php.net/bugs-generating-backtrace.php> I can't run httpd -X as suggested on that page because my version of Apache (1.3.19) doesn't support it. What can I do to get more debugging information so that this can get looked at? -- darron froese new media technologist sutton javelin corporate communications t 403.716.0351 f 403.265.7662 e darron@javelindigital.com