Re: [PHP4BETA] What about this?
| From: | Johan Isacsson | Date: | Tue, 28 Dec 1999 23:41:18 +0000 |
| Subject: | Re: [PHP4BETA] What about this? | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-8628@lists.php.net to get a copy of this message | ||
Hello,
Just wanted to say that i have the same problem, i have php cvs installed
on both a single and a smp box, so far this has only occured on the smp
box. I've tried poking with the core in gdb but i'm not very good at that
so if you have any check list that i can run when it happens that could
help :)
This nasty little bug kills apache so i have a cron job restart it every
hour, not a good solution but i'm in a situation where i can't go back to
php3 :P
So if there's anything i can do to help you nail it please tell me.
--------------------------------
Johan Isacsson
Generatorhallen
On Tue, 28 Dec 1999, Johan Ekenberg wrote:
> 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æfuÀÃ
> §VÝ1 ?|´/
>
>
> --
> PHP 4.0 Beta Mailing List <http://www.php.net/version4/>
> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net
> For additional commands, e-mail: php4beta-help@lists.php.net
> To contact the list administrators, e-mail: php4beta-admin@lists.php.net
>
>