Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62006
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
In-Reply-To: <CAPwsocF=bHLo6CH4iL-7QPsYkLOyB0cA6HHjLHLVHxuQayOmxw@mail.gmail.com>
References: <CAPwsocF=bHLo6CH4iL-7QPsYkLOyB0cA6HHjLHLVHxuQayOmxw@mail.gmail.com>
Date: Fri, 3 Aug 2012 22:27:48 +0800
Message-ID: <CABBJUpfEx854E1j4Xqvxd5ukTrgZ4HjSmE3Px890KtXgUrb47A@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Why do disabled functions / classes generate a WARNING.
From: laruence@php.net (Laruence)

On Fri, Aug 3, 2012 at 3:08 PM, Leigh <leight@gmail.com> wrote:
> Hi all,
>
> Can anyone explain to me the reason that when a function or class is
> disabled via the ini setting, an attempt to access the disabled item
> generates a non-fatal error?
>
> I'm looking at a segfault in the SPL caused by the blind creation of a
> class, which seems to only fail when the class is disabled. I'm
> wondering in how many other places this could occur.
>
> The obvious solution is to be more careful and check return values,
> but a FATAL would also have prevented execution continuing.
>
> Thanks,
>
> Leigh.
Hi:

this is a very badly bug.

but I think it's not a spl issues, we should change the behavior of
zend_disable_class,

since for now, it will delete the class entry, which will make the class entry
pointer (preserved by extension) become a wild pointer..

dereference it is a undefined behavior, in this sense, segfault is lucky.

thanks
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Laruence  Xinchen Hui
http://www.laruence.com/