Edit report at http://bugs.php.net/bug.php?id=52098&edit=1
ID: 52098 Updated by: fel...@php.net Reported by: jpa...@php.net Summary: Own PDOStatement implementation ignore __call() Status: Analyzed Type: Bug Package: PDO related Operating System: *nix & Win PHP Version: 5.3.2 Block user comment: N New Comment: I just fixed the SIGSEGV. Previous Comments: ------------------------------------------------------------------------ [2010-09-30 17:58:11] jpa...@php.net Has the patch been merged to 5.3.3 ? I'm still experiencing the bug on 5.3.3, please think about merging it to the right branch for the next release. Test would be great as well, I can manage that if you want. ------------------------------------------------------------------------ [2010-06-17 01:33:02] fel...@php.net Automatic comment from SVN on behalf of felipe Revision: http://svn.php.net/viewvc/?view=revision&revision=300504 Log: - New tests related to #52098 ------------------------------------------------------------------------ [2010-06-17 01:29:39] fel...@php.net I've committed a fix for the crash: http://svn.php.net/viewvc?view=revision&revision=300503 ------------------------------------------------------------------------ [2010-06-17 01:09:56] fel...@php.net I can reproduce it with another test case: <?php class MyStatement extends PDOStatement { } $obj = new MyStatement; var_dump($obj->foo()); Adding the support to __call lead to a strange behavior for classes that inherits PDOStatement. As it must be check if the called method is a user method or an driver method (which isn't stored in function_table) - that's when the instance is created by PDO object. If we introduce __call check, it must be done after the driver method checking... which will behave diferently when the instance is created by PDO or not... ------------------------------------------------------------------------ [2010-06-17 00:20:50] fel...@php.net I cannot reproduce the segmentation fault. ------------------------------------------------------------------------ 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 http://bugs.php.net/bug.php?id=52098 -- Edit this bug report at http://bugs.php.net/bug.php?id=52098&edit=1
