Bus Error/Coredump on Solaris 2.8 / Apache 1.3.19 / 4.0.4pl1

From: Date: Mon, 26 Mar 2001 16:16:43 +0000
Subject: Bus Error/Coredump on Solaris 2.8 / Apache 1.3.19 / 4.0.4pl1
Groups: php.dev 
Request: Send a blank email to php-dev+get-49963@lists.php.net to get a copy of this message
Hi, I'm experiencing recurring issues with stability on Solaris platforms. Using solely the standard XML functions and standard fsockopen() wrappers, I'm managing to get Apache/PHP to regularly coredump, and occasionally spew errors about functions it can't find in the file. Line numbers and function names are completely wrong, though. If I turn on debugging with --enable-debug, it works, after a fashion. To the end user it appears working, but in the Apache error log I keep getting lots of: [Mon Mar 26 17:39:07 2001] [notice] child pid 4902 exit signal Bus Error (10) [Mon Mar 26 17:39:07 2001] [notice] child pid 4901 exit signal Bus Error (10) [Mon Mar 26 17:39:08 2001] [notice] child pid 4904 exit signal Bus Error (10) [Mon Mar 26 17:39:08 2001] [notice] child pid 4903 exit signal Bus Error (10) My configure commandline: ./configure --prefix=/www --with-config-file-path=/www/conf --with-apxs=/www /bin/apxs --without-mysql --enable-debug My Apache setup is nothing nonstandard: ./configure --prefix=/www --enable-module=so I can't see what I'm doing wrong, I'm assuming there's a little platform idiosyncrasy somewhere, but have no idea where in the source to look (or how to debug Apache/PHP). Regards, Leon. -- System Administrator, iTouch Labs (Devco) GSM: +27-82-789-1245 Office: +27-21-415-2168 PGP Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x45EFAAE1

« previous php.dev (#49963) next »