Re: com php-src: Backported fix for bug #62852: NEWS ext/date/php_date.c ext/date/tests/bug62852.phpt ext/date/tests/bug62852_var2.phpt
ext/date/tests/bug62852_var3.phpt
| From: | Stas Malyshev | Date: | Wed, 20 Mar 2013 08:05:22 +0000 |
| Subject: | Re: com php-src: Backported fix for bug #62852: NEWS ext/date/php_date.c ext/date/tests/bug62852.phpt ext/date/tests/bug62852_var2.phpt ext/date/tests/bug62852_var3.phpt |
||
| References: | 1 2 3 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-71636@lists.php.net to get a copy of this message | ||
Hi!
> The issue is that a warning wouldn't destroy that object. That object will
> occasionally segfault PHP. E_ERROR is the simplest solution which doesn't
> change the behavior of the normal operations.
Can't we just reset the object data to some known "zero" state? Having
E_ERROR in a function that is not supposed to normally bail out is not a
good thing - especially unserialize which may deal with external data.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227