On Sun, 6 Mar 2005, Greg Beaver wrote: > We're getting quite a few reports of PEAR segfaulting on a > debug_backtrace() call found in the constructor of PEAR_Error. Jan > Schneider reported that it seemed to occur when one of the methods in > the trace happened in a file that the uid did not have write access to > (i.e. a PEAR file installed by root), but Davey Shafik posted a report > that it happened to him while running "pear upgrade PEAR" as root. He > also posted a backtrace that might be useful at: > > http://pear.php.net/bugs/bug.php?id=3683 > > Any tips on how to proceed in isolating this? I can't reproduce the > problem on any of my systems (windows xp, gentoo).
Disable the memory manager in zend_alloc.h (it's a define "ZEND_ALLOC" afaik). Then use valgrind to run PHP and see whether it shows errors... regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
