Edit report at https://bugs.php.net/bug.php?id=61541&edit=1
ID: 61541
Updated by: yohgaki@php.net
Reported by: grzegorz129 at gmail dot com
Summary: Segfault using ob_clean/flush* functions in
output_callback function
-Status: Open
+Status: Closed
Type: Bug
Package: Reproducible crash
Operating System: ANY
PHP Version: 5.3
-Assigned To:
+Assigned To: yohgaki
Block user comment: N
Private report: N
New Comment:
patch is merged.
Thank you.
Previous Comments:
------------------------------------------------------------------------
[2012-03-28 23:55:46] reeze.xia@gmail.com@php.net
Automatic comment on behalf of reeze.xia@gmail.com
Revision: http://git.php.net/?p=php-src.git;a=commit;h=9bc91a21db733b5e12ab6a4356b2470b72d784d5
Log: - fix bug #61541, Segfault when using ob_* in output_callback
------------------------------------------------------------------------
[2012-03-28 23:55:45] reeze.xia@gmail.com@php.net
Automatic comment on behalf of reeze.xia@gmail.com
Revision: http://git.php.net/?p=php-src.git;a=commit;h=abd2b2ee4332e598f46efec0cac0a9f546bc4f2d
Log: - fix bug #61541, Segfault when using ob_* in output_callback
------------------------------------------------------------------------
[2012-03-28 19:21:28] yohgaki@php.net
I thought it worked for old PHPs, but it's not. So it would be OK to raise fatal
error. Restored version.
I'll just add recursive call error to 5.3.
------------------------------------------------------------------------
[2012-03-28 19:04:31] grzegorz129 at gmail dot com
@mike - nooone like crashes but it should work instead of throwing E_FATAL. This
kind of (tricky) code as I know is only way to catch errors which
set_error_handler() just can't catch. If you know another way to do this propose,
please.
------------------------------------------------------------------------
[2012-03-28 19:01:31] mike@php.net
Sure, it raises a fatal error, because I don't like crashes.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=61541--
Edit this bug report at https://bugs.php.net/bug.php?id=61541&edit=1