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

> This is probably just another instance of a bug believed to > be fixed (Thies, you probably remember the SMP-issues on > Linux WRT time out). Sascha: I believe I was the first one to report on this bug (Bug ID 2866) and, as you may recall, I also tried one or two of your patches - without success. Progress was discontinued when I could not use CVS version later than mid-Dec, due to serious segfaults on all mysql-operations. Today I have more or less successfully managed to put up the latest CVS (2000-02-16). Not completely successful since there are still child-httpd-segfaults pertaining to mysql-functions, but it seems to be good enough for running a couple of days. Do you want me to try any new patches? Should I try to apply the last one you sent (it was never tried due to the MySQL issue). I've attached it to this mail. I have not run the latest compile long enough to tell that the bug is still present (core httpd SIGSEGV, Apache completely dies), but I'll let you know when (if) it happens. Best regards, /Johan Ekenberg

Index: main.c =================================================================== RCS file: /repository/php4/main.c,v retrieving revision 1.170 diff -u -r1.170 main.c --- main.c 2000/01/01 01:31:27 1.170 +++ main.c 2000/01/04 00:45:29 @@ -476,8 +476,10 @@ PLS_FETCH(); PG(connection_status) |= PHP_CONNECTION_TIMEOUT; +#ifdef PHP_ERROR_REENTRANT php_error(E_ERROR, "Maximum execution time of %d second%s exceeded", php_timeout_seconds, php_timeout_seconds == 1 ? "" : "s"); +#endif } #endif