#48634 [Fbk->Opn]: Calling ob_get_flush() inside an output handler causes crashes
| From: | gwynne@php.net | Date: | Sat, 18 Jul 2009 01:42:45 +0000 |
| Subject: | #48634 [Fbk->Opn]: Calling ob_get_flush() inside an output handler causes crashes | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-139893@lists.php.net to get a copy of this message | ||
ID: 48634
Updated by: gwynne@php.net
Reported By: gwynne@php.net
-Status: Feedback
+Status: Open
Bug Type: Reproducible crash
Operating System: Darwin9 (MacOS X 10.5)
-PHP Version: 5.3CVS-2009-06-22 (CVS)
+PHP Version: 5.2SVN, 5.3SVN, HEAD SVN
New Comment:
Yes, it happens in all three branches.
Previous Comments:
------------------------------------------------------------------------
[2009-07-17 17:40:04] jani@php.net
Does this happen with PHP_5_2 and/or HEAD? (if so, update the version
properly)
------------------------------------------------------------------------
[2009-06-22 00:34:03] gwynne@php.net
Description:
------------
The subject kind of says most of it. Under both GDB and Valgrind, PHP
enters a massive recursion until it finally crashes by overrunning the
stack, which is expected, according to a comment in a test that a fix
needs to be backported from HEAD. So this bug is mostly about "please
backport this fix", I suppose.
Reproduce code:
---------------
See tests/output/ob_11.phpt
Expected result:
----------------
A fatal error saying "you can't do that".
Actual result:
--------------
Endless recursion.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=48634&edit=1