php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #35257 Calling ob_flush after creating an ob callback causes "Segmentation fault"
Submitted: 2005-11-17 12:01 UTC Modified: 2005-11-17 16:21 UTC
From: maddog2k at maddog2k dot net Assigned:
Status: Closed Package: Output Control
PHP Version: 4.4.1 OS: Linux
Private report: No CVE-ID: None
View Developer Edit
 [2005-11-17 12:01 UTC] maddog2k at maddog2k dot net 
Description:
------------
This is a copy of bug #35156, which is closed...

The code there still segfaults with php4-STABLE-200511160748 (combined with at least Apache 2.0.54/.55).

I disabled Zend Optimizer, no change.

I've put ob_* functions now into 'disabled_functions' and the logs (Shared Hosting Server) remain free from Segmentation faults.

Reproduce code:
---------------
(taken from bug #35156)

<?php 
function nooutput($text) { return ""; } 
print "Before\n"; 
ob_start("nooutput"); 
print "Middle\n"; 
ob_flush();
ob_end_flush(); 
print "After\n"; 
?> 

Expected result:
----------------
(taken from bug #35156)

Before
After


Actual result:
--------------
Apache child Segmentation fault

[Thu Nov 17 11:08:59 2005] [notice] child pid 4657 exit signal Segmentation fault (11)

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-11-17 12:42 UTC] tony2001@php.net 
This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.
 [2005-11-17 16:21 UTC] maddog2k at maddog2k dot net 
Yes, it's fixed :)
Many thanks !
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sat Feb 22 17:01:28 2025 UTC