#25713 [Bgs]: endless self call loop
| From: | moriyoshi@php.net | Date: | Wed, 01 Oct 2003 17:34:41 +0000 |
| Subject: | #25713 [Bgs]: endless self call loop | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-48389@lists.php.net to get a copy of this message | ||
ID: 25713
Updated by: moriyoshi@php.net
Reported By: kevin at netflex dot nl
Status: Bogus
Bug Type: Reproducible crash
Operating System: Windows/Netware and maybe more
PHP Version: 4.3.3
New Comment:
Anyway, that's expected behaviour as stated in other bug reports.
Previous Comments:
------------------------------------------------------------------------
[2003-10-01 13:23:07] moriyoshi@php.net
You should first try hard to crash it with that tiny script.
If it really was to go wrong, then reopen this bug to let us know what
did actually happen on your server :)
------------------------------------------------------------------------
[2003-10-01 11:49:00] kevin at netflex dot nl
i know, (mistake from me ;-).
But now the problem is that i can crash the server if i want by making
an endless loop (with calls).
------------------------------------------------------------------------
[2003-10-01 11:36:57] moriyoshi@php.net
function crash(&$test) {
if ($test < 10)
crash($test);
$test++;
}
There's no chance $test is incremented. So no matter how the variable
is passed to the function, it will definitely go into an infinite loop
and end up eating up all the stack area which really causes
segmentation fault.
------------------------------------------------------------------------
[2003-10-01 11:14:45] kevin at netflex dot nl
1. we did
2. buffer overflow?? is this normal for you??
3. i don't agree, i could crash any php hosting if i want.
;-)
------------------------------------------------------------------------
[2003-10-01 10:33:30] sniper@php.net
1. You didn't search the bug database first
2. This is expected.
3. We won't "fix" it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/25713
--
Edit this bug report at http://bugs.php.net/?id=25713&edit=1