jvlad wrote:
#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 :)
Here? Yea, it is. But looking at the libapr-1.so.0 module, agreed that
I've misread this :)
@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?
I'm not used to seeing bad stack unwinds on unix, most people don't optimize
that aggressively.
If this is system-httpd, that's fine; if you installed an httpd package,
there is likely an httpd-devel package that also includes the debugging
symbols you need (unstripped).
If not and you've built this, you can simply try -O0, or -g, or for httpd
--enable-maintainer-mode, but offhand I can't think of a trivial way to
simply avoid -strip, which is what you want for your build when things
go wonky in your gdb where output.
Bill
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
