Edit report at https://bugs.php.net/bug.php?id=52565&edit=1
ID: 52565 Updated by: [email protected] Reported by: martin dot minka at gmail dot com Summary: print out of Zend_Form causing segmentation fault -Status: Feedback +Status: No Feedback Type: Bug Package: Reproducible crash Operating System: Linux PHP Version: 5.3.3 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2010-09-29 15:33:10] [email protected] Without using Zend Forms? So what was the test case? Can you provide a short script? :) ------------------------------------------------------------------------ [2010-09-29 15:31:20] yesin dot iv at gmail dot com Got same backtrace without using Zend Forms. ------------------------------------------------------------------------ [2010-08-09 10:46:54] [email protected] Ah sorry, I did not see the attachment. However ZF is not exactly a small self contained reproduce script. I would suggest to either try to debug it or ask the ZF devs to debug. Maybe you are experiencing Mike's issue as well. ------------------------------------------------------------------------ [2010-08-09 10:43:19] martin dot minka at gmail dot com Thank you for quick reactions. I compiled PHP with debug enabled and produced backtrace. It is attached in patch section. Reproduce script is included in the original text. That exact script crashes for me everytime. ------------------------------------------------------------------------ [2010-08-09 09:41:57] [email protected] IIRC there's a place in (older version of?) the ZF Form libs where __toString() does not return a string, causing a unexpected SIGSEGV. ------------------------------------------------------------------------ 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=52565 -- Edit this bug report at https://bugs.php.net/bug.php?id=52565&edit=1
