Edit report at https://bugs.php.net/bug.php?id=62854&edit=1
ID: 62854 Updated by: fel...@php.net Reported by: popsul1993 at gmail dot com Summary: Segfault on call_user_func_array -Status: Open +Status: Not a bug Type: Bug Package: Reproducible crash Operating System: Ubuntu 12.04 PHP Version: 5.4.6 Block user comment: N Private report: N New Comment: Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php It's expected, your code is causing a call stack overflow. Previous Comments: ------------------------------------------------------------------------ [2012-08-20 05:59:26] larue...@php.net is that a stack overflow segfault? ------------------------------------------------------------------------ [2012-08-20 01:31:32] ahar...@php.net I think Felipe thought you were talking about the whole bug in the first comment, not just that paragraph. Reopened. ------------------------------------------------------------------------ [2012-08-18 15:53:24] popsul1993 at gmail dot com Why that not a bug? Interpreter crashes when recursion is over call_user_func_array, and necessary make Fatal Error. IF that code running under php 5.3 - behavior is correct, and under 5.4 - interpreter crash with segfault. p.s. Sorry for my English. ------------------------------------------------------------------------ [2012-08-18 15:13:21] fel...@php.net . ------------------------------------------------------------------------ [2012-08-18 14:21:34] popsul1993 at gmail dot com > Also, PHP >=5.4.5 have a crazy behavior, i.e. my implementation of ActiveRecord > have method 'buildSql' (with public visibility), but when run e.g. $this- >buildSql(); > that call send to __call(), where there is a checing with code > method_exists($this, $method_name), which returning true and after that calling > call_user_func_array([$this, $method_name], $parameters);, and that > invocation > again sending to __call(), although method buildSql exists and visibled. that bug already resolved and fixed, autoreplace error. sorry. ------------------------------------------------------------------------ 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=62854 -- Edit this bug report at https://bugs.php.net/bug.php?id=62854&edit=1
