Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43985
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.166 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=mWszLTTVou8C38mmTyJeCWjUFAmoRVeO3M1WP76ewWR/UJkF+iCMMDKLMn3eBA/eMs
         Oe/dMaajfojI0I7GhDJljjZMx+NGJNSHsbo1EcUEaVCSocs9VrlXUqh8hyNY6/trw2N7
         61pKyj78n+g/5o/OU/qnXNdfJMyVUk4Q0B4vc=
MIME-Version: 1.0
In-Reply-To: <cd1fb7540905142113l773b09c3s74960737e60d5e68@mail.gmail.com>
References: <c6f9c9e70905142031u49874dbifd19fdd340b0c702@mail.gmail.com> 
	<cd1fb7540905142113l773b09c3s74960737e60d5e68@mail.gmail.com>
Date: Fri, 15 May 2009 08:07:00 -0400
Message-ID: <c6f9c9e70905150507t4485a9b3td150cd30e0e6e39e@mail.gmail.com>
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Segfault while looping through hash table
From: farleyknight@gmail.com (Farley Knight)

On Fri, May 15, 2009 at 12:13 AM, Moriyoshi Koizumi <mozo@mozo.jp> wrote:
> On Fri, May 15, 2009 at 12:31 PM, Farley Knight <farleyknight@gmail.com> =
wrote:
>
>> =A0zend_hash_internal_pointer_reset(Z_ARRVAL(zhash));
>>
>> =A0printf("This hash table has %d entries\n",
>> zend_hash_num_elements(Z_ARRVAL(zhash)));
>>
>> =A0int current =3D 0;
>>
>> =A0while (zend_hash_get_current_data(Z_ARRVAL(zhash), (void**)&value)
>> =3D=3D SUCCESS) {
>> =A0 =A0current++;
>> =A0 =A0printf("Currently on entry %d\n", current);
>> =A0 =A0if (zend_hash_move_forward(Z_ARRVAL(zhash)) =3D=3D SUCCESS)
>> =A0 =A0 =A0printf("Done moving hash forward. Result was successful\n");
>> =A0 =A0else
>> =A0 =A0 =A0printf("Done moving hash forward. Result was a failure\n");
>> =A0}
>>
>
> Does the problem persist if replacing the hashtable functions by the
> _ex counterparts: zend_internal_pointer_reset_ex(),
> zend_hash_get_current_data_ex() and zend_move_forward_ex()? These are
> always recommended (I believe) because the internal HashPosition value
> associated to a hashtable is also used in the user script.
>
> Regards,
> Moriyoshi
>

Actually I believe I did, but if they are recommended, I suppose I
will use them instead. Thanks for pointing that out.

BTW I did provide a link to the rest of the code, but I realize what I
posted above might not be enough to understand where the bug lies.
Should I bother posting a larger portion?

Thanks,
- Farley