#29735 [Opn->Bgs]: Segfault (11) / Possible stack corruption
| From: | derick@php.net | Date: | Wed, 18 Aug 2004 13:48:00 +0000 |
| Subject: | #29735 [Opn->Bgs]: Segfault (11) / Possible stack corruption | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-64852@lists.php.net to get a copy of this message | ||
ID: 29735
Updated by: derick@php.net
Reported By: sparkeh at btinternet dot com
-Status: Open
+Status: Bogus
Bug Type: Reproducible crash
Operating System: Linux 2.6.7-gentoo-r9
PHP Version: 5.0.1
New Comment:
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
This is expected, PHP does not protect against infinite recursion.
Previous Comments:
------------------------------------------------------------------------
[2004-08-18 15:24:10] sparkeh at btinternet dot com
Description:
------------
I've tried to get the code to the minimum required to cause a crash.
The combination of the local variable being defined and the global
reference seems to be causing stack corruption (the script never
returns successfully from the function call:
jelly can # php -f crash.php
About to segfault : Segmentation fault
jelly can # php -v
PHP 5.0.1 (cli) (built: Aug 18 2004 12:39:38)
Reproduce code:
---------------
<?
switch($t)
{
default:
$rar = 0;
function segfault()
{
global $moo;
echo 'About to segfault : ';
}
segfault();
}
?>
Expected result:
----------------
About to segfault :
Actual result:
--------------
About to segfault : Segmentation fault
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=29735&edit=1