Sent from my iPhone

在 2012-1-25,15:49,Dmitry Stogov <dmi...@zend.com> 写道:

> On 01/25/2012 11:36 AM, Rasmus Lerdorf wrote:
>> Still a known crash bug though. This is what our RCs are supposed to
>> catch, right?
>
> This is not a single way to crash PHP with especially prepared code.
> Some of these ways are never going to be fixed.
>
> For me it doesn't mater if this patch will be committed before or after 
> release. Anyway, the patch may have effect only on very specific PHP code and 
> shouldn't make any harm.
>
Indeed, I think we should been careful with *big* patch which might
introduce new issues when in code freeze phase.

Considering this little fix, it is no harm to  commit to RC. :)

Anyway it also okey for me to commit after release, since this is
really a trivial bug and there are already  one patche for me need to
be remembered ci after 5.4.0 released. :)

Thanks

> Thanks. Dmitry.
>
>> On 01/24/2012 11:34 PM, Dmitry Stogov wrote:
>>> Hi Stas,
>>>
>>> Not a big problem, just yet another way to crash PHP locally with tricky
>>> code. It may be committed after release as well.
>>>
>>> Thanks. Dmitry.
>>>
>>> On 01/25/2012 11:29 AM, Stas Malyshev wrote:
>>>> Hi!
>>>>
>>>>> Now it looks fine.
>>>>> I think it should be committed into 5.4 as well.
>>>>> Stas?
>>>>
>>>> That would probably require new RC, i.e. release will have to be pushed
>>>> back. How serious is the problem we're talking about?
>>>>
>>>
>>>
>>
>

--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to