Re: SV: [PHP4BETA] SV: [PHP-DEV] PHP 4.0 Bug #3497 Updated: Apache 1.3.11 gets SIGSEGV immediately qafter start

On Thu, 17 Feb 2000, Johan Ekenberg wrote: > > i'm pretty sure that the SIGSEGV is the parent apache-process > > is fixed in CVS! > > > > tc > > Thies: > > Unfortunately I was never able to run the "16 feb CVS" long enough to > verify this. The children started segfaulting pretty badly, mostly > on different MySQL related stuff, but also when getting pictures, > cgi's - you name it. Some users started reporting the well known > "PHP Fatal error: Maximum execution time of 20 seconds exceeded > in [no active file] on line 0" error. > At this time I bailed out and returned to beta 2. Unfortunately I > can't take the time to do serious debugging on these servers > since they're in heavy production use, and it's hard to emulate > the high load on a test server. > > What's more, as you yourself reported, the PHP_AUTH_USER/PHP_AUTH_PW > vars where out of order. I never saw a reply to your post about that, > did it get corrected? They've been fixed. > Isn't it a strange thing that beta 2 is the stablest version I can find? > Somewhere mid December things started to go bad with mysql_*() that > produces crasches on my machines. Apart from an occasional parent > apache-process total crash, beta 2 seems quite stable and functional here. > I've got a surveillance script running every minute that fires up Apache > again when parent-pid crashes happen - every few hours or so. Make no mistakes, Beta 2 is much, much buggier than Beta 3, and than the current CVS. I'll take a look at your bug reports and try to figure out what's going on, but the thousands of changes since Beta 2 aren't going to be reversed :) Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/