Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_constants.c

> > valgrind is a nice tool but it's still not the voice of God. A memory > overrun or an uninitialized memory read is a *symptom*, not a source of a > problem. In this particular case, it's much more likely that the code that > was touching EG(uninitialized_zval) shouldn't have been doing it. As such > the early initialization does appear to be a voodoo fix, and the real fix > would be determining why EG(uninitialized_zval) is even being touched at > this stage. because you should not use any zval* functions in any *Ini* related function. (RTA - Read the Archives) as this special case doesn't really do anything bad i have left it in (the module in question was written by me) - but i think we should find a real solution for problems like this which make sure (atleast in debug-builds) that we don't depend on parts of the engine (in this case the zval-"manager") when we should not (in the ini-system). re, tc