On Thu, 18 Dec 2003, Pierre-Alain Joye wrote: > On Thu, 18 Dec 2003 13:50:10 +0100 (CET) > Derick Rethans <[EMAIL PROTECTED]> wrote: > > > On Thu, 18 Dec 2003, Pierre-Alain Joye wrote: > > > > > 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. > > > > Can you put the datafile + serialize call in a test case? > > I tried (see links below), but a simple test case does not segfault > with the same file. > > Please note a weird notice about an undefined $data variable. The > problem is that $data is a function argument and is used in the 1st line > of the functon... Any idea? > > One of the serialized data which cause the segfault: > http://www.pearfr.org/~paj/pear/packageserialized > > A patch against /php-src/pear/ to see where that happens and to > reproduce the weird notice: > http://www.pearfr.org/~paj/pear/pear-install-seg.patch > > A useless test case: > http://www.pearfr.org/~paj/pear/test_seg.php > > It works perfectly, but the same file and code segfaults in PEAR. > > A bit lost right now, memory issue?
Guesso... can you try to run it in valgrind, it should show all memory overruns etc.. Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
