Edit report at https://bugs.php.net/bug.php?id=64168&edit=1
ID: 64168
Updated by: larue...@php.net
Reported by: rosier at interstroom dot nl
Summary: Segmentation fault when a Closure ends up in the
session data
-Status: Open
+Status: Feedback
Type: Bug
Package: Session related
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
I can not reproduce this with 5.4.* , could you please paste the backtrace out?
Previous Comments:
------------------------------------------------------------------------
[2013-02-07 09:29:12] rosier at interstroom dot nl
Description:
------------
I can reproduces the segfault with PHP 5.3.21 and PHP 5.4.11
Test script:
---------------
session_start();
$_SESSION['test'] = function($name) { return strtoupper($name); };
Expected result:
----------------
No crash and a error message like "PHP Fatal error: 'Closure' in session data
is not allowed"
Actual result:
--------------
Blank screen in the browser and the following apache logs:
[Wed Feb 06 12:51:50 2013] [error] [client 192.168.0.xx] PHP Fatal error:
Uncaught exception 'Exception' with message 'Serialization of 'Closure' is not
allowed' in [no active file]:0\nStack trace:\n#0 {main}\n thrown in [no active
file] on line 0
[Wed Feb 06 12:51:51 2013] [notice] child pid 7316 exit signal Segmentation
fault (11)
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=64168&edit=1
