Stas,
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.
There is another one bug #53437. The patch there has E_ERROR as well, but
for the same reason.
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
On Wed, March 20, 2013 09:05, Stas Malyshev wrote:
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
Commit:8d199c7c4f93ebe5b9293096143d7007a6ad13a4
Author:Anatol Belski a...@php.net Tue, 19 Mar 2013 21:19:55 +0100
Parents: 4a6291508d69fab951562b996ed7223c052a0168
Branches: PHP-5.3 PHP-5.4 PHP-5.5 master
Link:
Hi!
+ if (!php_date_initialize_from_hash(return_value, dateobj, myht
TSRMLS_CC)) {
+ php_error(E_ERROR, Invalid serialization data for DateTime
object);
+ }
Why this is E_ERROR? Can't we recover from this problem? Bad
serialization data is E_NOTICE for unserialize(),
