""William A. Rowe, Jr."" <wr...@rowe-clan.net> wrote in message news:49cb613b.4070...@rowe-clan.net... > Rathnakar Konda wrote: >> after observing lots of core dumps from apache, we got a different >> segfault and its back trace is given bellow >> >> #0 0x00002aaab1c46688 in ZEND_FETCH_DIM_RW_SPEC_VAR_UNUSED_HANDLER ( >> execute_data=0x5555714ea6c8) >> at /usr/local/src/php/php-5.2.9/Zend/zend_vm_execute.h:13204 >> opline = (zend_op *) 0x5555714e8798 >> free_op1 = {var = 0x2aaaac1454fd} > > you appear to have .pdb symbols for your php. Now you need them for > apache... > >> #2 0x00002aaaac145afb in apr_pool_destroy () from >> /usr/lib64/libapr-1.so.0 >> No symbol table info available. > > See http://httpd.apache.org/dev/debugging.html on how to grab the > -win32-symbols.zip package. Unpack it over httpd and you will probably > have more legible backtraces. Ensure you have all the debugging symbols > for php you'll have something completely legible.
aha, and /usr/local/src/php/php-5.2.9/Zend/zend_vm_execute.h is a very common path under Win32 :) @Rathnakar Konda, is it possible that php was compiled against wrong Apache headers? Did you install something like OS-supplied httpd-devel package to compile php or grabbed apache sources from their web site? -jv -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
