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

go to bug id or search bugs for

Bug #35939 SPL ArrayObject segmentation fault when more than one parameters passed
Submitted: 2006-01-09 09:11 UTC Modified: 2006-01-10 07:11 UTC
From: lynjwxm at hotmail dot com Assigned: helly (profile)
Status: Closed Package: SPL related
PHP Version: php5-STABLE-200509220445 OS: *
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: lynjwxm at hotmail dot com
New email:
PHP Version: OS:

 

 [2006-01-09 09:11 UTC] lynjwxm at hotmail dot com 
Description:
------------
If you give more than one parameters to function ArrayObject::__construct(),it really crashed.I know I did not use this function correctly, but I did not expect the segmentation fault. I expect a warning of uncaught exception not a seg fault.

Reproduce code:
---------------
<?php
$test=array("cat","dog","it","rains");
//try{  //comment exception catcher cause crash.
        $obj=new ArrayObject($test,5);
//}catch(Exception $e)
//{
        echo "exception protect you.\n";;
//}
var_dump($obj);
?>


Expected result:
----------------
anything other than crash

Actual result:
--------------
segmentation fault

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-01-09 09:19 UTC] sniper@php.net 
Marcus, latest CVS does not crash but doesn't give any error either. Intentional or not?
 [2006-01-09 20:46 UTC] helly@php.net 
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 cannot reproduce this and valgrind doesn't find anything. So please update to 5.1.2-RC2 and test again. If it still happens send me a backtrace as explained above.
 [2006-01-10 07:11 UTC] lynjwxm at hotmail dot com 
I am sorry that I made a mistake about the version of php with which I produced this defect. I use php5-STABLE-200509220445 to do so. I download the latest php-5.1.2RC1 only to find it has gone. Still need backtrace?
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Tue May 13 12:01:27 2025 UTC