Re: B3, pear segfault

From: Date: Thu, 18 Dec 2003 21:54:49 +0000
Subject: Re: B3, pear segfault
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-6562@lists.php.net to get a copy of this message
Hi, as I wrote in my initial post: Even changing the paramters for pear/install-pear.php "helps" and I am not able to create a simpler script reproducing the crash. But meanwhile I've found the time when it broke: zend_execute.c,v 1.565 2003/12/14 16:09:07 still works but zend_execute.c,v 1.566 2003/12/15 07:22:09 breaks. So this seems to be the causing commit: http://lists.php.net/article.php?group=php.zend-engine.cvs&article=2118 maybe it helps... Zeev Suraski wrote:
Any chance you can dissect it to the smallest piece of code that still produces the crash? At 14:46 18/12/2003, Pierre-Alain Joye wrote:
On Thu, 18 Dec 2003 12:43:03 +0100 Pierre-Alain Joye <paj@pearfr.org> wrote:
Hello, I'm trying to see why $ make install-pear-packages segfaults with HEAD. I hope I'll commit the fixes today. I suspect references problem... I got new messages (which where not displayed before): : var: Deprecated. Please use the public/private/protected modifiers in XXX.php on line XX Have these warning/notices been introduced recently? Or is it related to the e_pedantic thing?
Ok segfault is on line pear/PEAR/Registry.php line 345. This is a call to unserialize. I do not know yet why it fails. Maybe (again) the serialized data is corrupted. Anyway unserialize should ""never"" segfault. hth pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.internals (#6562) next »