Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71250
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH8MpnmBNWC1Kk2cadHyDkNJs_Vq6JXHHiSmG10HRKvAMaR-SA@mail.gmail.com>
References: <CAH8MpnmBNWC1Kk2cadHyDkNJs_Vq6JXHHiSmG10HRKvAMaR-SA@mail.gmail.com>
Date: Sun, 19 Jan 2014 03:52:47 +0800
Message-ID: <CAKSD0w725avbxUvPmLbszK5Ynx+QTYbp+UgeoxG0Xwig8mZWpQ@mail.gmail.com>
To: Daniel Lowrey <rdlowrey@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=90e6ba6134bebbdca304f044004e
Subject: Re: How to create Persistent zval?
From: cornelius.howl@gmail.com (Lin Yo-An)

--90e6ba6134bebbdca304f044004e
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: quoted-printable

Daniel Lowrey <rdlowrey@php.net> =A9=F3 2014=A6~1=A4=EB19=A4=E9=ACP=B4=C1=
=A4=E9=BCg=B9D=A1G

> >> Hello,
> >>
> >> I am trying to store a zval object into the persistent list in zend VM=
.
> >> (Using EG(persistent_list) and zend_rscd_list_entry)
> >>
> >> Which works fine if I store/fetch the zval in the same request context=
.
> >>
> >> But it seems that zend engine cleans up the zval object after the
> request,
> >> when the next request comes, the fetched list entry points to a freed
> zval
> >> address and it makes php segmentationfault. I guess zval is allocated =
by
> >> emalloc, so I cant keep it cross requests?
>
> > For persistent alloc, you should use pemalloc() , which is just a
> > wrapper leading to libc's malloc.
> > If you use emalloc() , the Zend Memory Manager will free the storage
> > at the end of the request, thus leading to use-after-free crash if you
> > reuse your pointer on a next request.
>
> --- Disclaimer ---
> I'm passing this along; Joe is having technical difficulties and asked fo=
r
> help sending this to the list. I provide no warranties or refunds ;)
> ---
>
> All zvals passed into the engine must be allocated by the mm, you cannot
> pemalloc anything and pass it into the engine safely.
>
> You don't want to store a persistent zval, you want to store a persistent
> resource entry, which should be allocated with pemalloc(size, 1)
>
> The reason for this is when cleaning up, the engine has no means by which
> to tell if a zval has been pemalloc or emalloc'd, zval_ptr_dtor works the
> same for everything.



Thank you so much! That is what i was guessing..  - ref cnt and pemalloc
does not work for persistent zval.

And zend engine cleans up zvals at the end of request no matter the ref cnt
is?

so zval is not persistent, then is HashTable persistent?

It's because I need to store a zval object which has several properties.
 Is there a way to do make the object persistent? Or do i need to serialize
it just like apc?



> Cheers
> Joe
>


--=20
Best Regards,

Yo-An Lin

--90e6ba6134bebbdca304f044004e--