What about this?

I've been reporting on a serious bug for about a month, testing different setups and the latest CVS-versions. The bug is a major segfault causing the main httpd-process (Apache) to crash, bringing down the entire Apache server. (It is _not_ only a segfault in a child process). The bug was reported duplicated by Lars Magne Ingebritsen (larsi@gnus.org) on this list in mid-December. So far there has been very little response from the major developers. This is *NOT* a complaint. I'm most grateful and impressed by the work being done on PHP4. What I want to know is if there is anything more that I can do to help nail this bug. ?? Below is the latest update I made to the bug database. Lars Magne said it only affects his SMP machines, but since I'm only running SMP I can't verify this. But it may explain why it's not often reported (?). Best regards, Johan Ekenberg ============ ID: 2866 User Update by: johan@ekenberg.nu Status: Analyzed Bug Type: Other Description: Apache dumps core and dies, segfault at mod_php4.c:168 Crashes still occur with CVS 23/Dec/99. There are some indications that this might only pertain to SMP machines. Error log still reports "PHP Fatal error: Maximum execution time of 20 seconds exceeded in [no active file] on line 0". Please observe "[no active file], and line 0", but a test shows that a regular max_execution_time timeout will show a real file and line number in the logs. Backtrace: Cannot access memory at address 0x40007138. #0 0x80ccf9e in sapi_apache_send_headers (sapi_headers=Cannot access memory at address 0xbfffeef0. ) at mod_php4.c:208 208 ((request_rec *) SG(server_context))->status = SG(sapi_headers).http_response_code; Full Bug description available at: http://bugs.php.net/version4/?id=2866