Re: [PHP4BETA] Memory Fault in Apache on OpenBSD 2.5

On Wed, Aug 11, 1999 at 07:56:24AM -0400, George Hartz wrote: > Jeff Johnson wrote: > > > > I'm having problems getting PHP/4.0B2 up as an internal Apache module. > > The system is OpenBSD 2.5, GCC 2.95. It working fine with: > > > > Apache/1.3.6 (Unix) DAV/0.9.8 mod_fastcgi/2.2.2 mod_macro/1.1.1 > > mod_perl/1.21 mod_ssl/2.3.11 OpenSSL/0.9.4 > > > > ...right now. I haven't tried PHP3 on it yet, as all of the other > > servers are PHP4, and I'd prefer to keep them all on the same version. > > That's interesting, I have the same problem with a 1.3.6, only under > Linux not OpenBSD. I had better luck using DSO rather than compiling it > into the server -- then it only craps out on certain pages, instead of > on startup. I'd prefer not to use DSO's for certain reasons, mainly to keep the build script portable between all of the computers here at the office. I guess if it comes down to needed PHP/4, this will have to be done. > What's interesting is that you're using mod_ssl in the server... the two > servers I had that coredump problem with both were using mod_ssl as > well, which extends the Apache module API. Perhaps that's related? Are > you able to build you server without mod_ssl? Unfortunately I'm not able > to, because its a binary-secure server so I can't rebuild the exact same > server without the ssl to see if that might be related. One thing to note is that I configured PHP into the server (APACI method) before configuring mod_ssl into the server. Maybe we can try reversing the order, installing mod_ssl which installs EAPI (and the EAPI_MM hooks I believe), and then configuring PHP. I don't see how it would make a difference, however. Unfortunetly, mod_ssl is more of a requirement for the application than PHP/4 is. Interesting note follows, about PHP/3, however... > Not sure if they're related, but its something for everyone who's having > that problem to think about... maybe I'll throw a stock Apache on a test > machine and see if I can duplicate the problem w/out mod_ssl... > > - George I did a little further testing, compiling PHP/3.0.12 into the server with the exact same options, and PHP/3 works perfectly, no crashing, so it is definately an issue with PHP/4b. Are there possibly interactions with GCC 2.95 in which PHP/4 is known to fail? Another interesting note, I couldn't get my Solaris x86 2.7 machine to run the Apache server with this configuration using GCC 2.8.1... the server would Segmentation Fault on startup, but everything is working fine after an upgrade to GCC 2.95. On another box (FreeBSD 3.2-STABLE), httpd cores when compiled with GCC 2.95, but using the system GCC 2.7.2.3 works. Another thing I'm noticing with GCC 2.95 is broken code produced with -fPIC enabled. I've upgraded from the stock as to GNU gas 2.9.1 with the same results. However, this doesn't prevent anything from working as far as I can see (not using -fPIC), believe it or not. Bizareness.... Unfortunetly, once again, we need GCC 2.95 (or at least a recent egcs release) to compile some of our C++ code which uses things like exceptions heavily. Lately, it seems like my Solaris workstation runs flawlessly compared to these odd compatibility problems we have been having on our OpenBSD and FreeBSD servers, and it seems tempting to try to talk the men upstairs into purchasing a few Ultra's if our problems continue. So much for free software, when it costs more to maintain than a boxed solution. -- Jeffrey H. Johnson, jeff@websitefactory.net The Web Site Factory, http://www.websitefactory.net