Edit report at http://bugs.php.net/bug.php?id=48634&edit=1
ID: 48634
Updated by: ka...@php.net
Reported by: gwy...@php.net
Summary: Calling ob_get_flush() inside an output handler
causes crashes
-Status: Open
+Status: Feedback
Type: Bug
Package: Reproducible crash
Operating System: Darwin9 (MacOS X 10.5)
PHP Version: 5.* (2009-07-25)
Block user comment: N
Previous Comments:
------------------------------------------------------------------------
[2010-09-20 02:17:39] ka...@php.net
Wasn't this fixed with the backport of the ob handling API in trunk?
------------------------------------------------------------------------
[2009-07-21 12:04:22] gwy...@php.net
Correction: This does NOT happen in HEAD.
------------------------------------------------------------------------
[2009-07-18 01:42:45] gwy...@php.net
Yes, it happens in all three branches.
------------------------------------------------------------------------
[2009-07-17 17:40:04] j...@php.net
Does this happen with PHP_5_2 and/or HEAD? (if so, update the version
properly)
------------------------------------------------------------------------
[2009-06-22 00:34:03] gwy...@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/bug.php?id=48634&edit=1
