Re: 64 bit platform improvements

Jan, On Sat, December 28, 2013 19:18, Jan Ehrhardt wrote: > Jan Ehrhardt in php.windows (Sat, 28 Dec 2013 17:53:13 +0100): > >> Silly design of DebugDiag. Why does not it look by default in the >> directory where the DLL is located? VC does it that way.... >> >> I am now putting then in c:\symcache, which seems to be the default >> directory. >> >> >> Edit: Google told me the full pdb-path is in the DLL, i.e. where it was >> built: C:\php-sdk\phpint64\x64\Debug\php5_debug.pdb. So probably not >> cleaning you build directories will work as well. > > Neither of those: you have to point to the dir where they were built. > And then you'll get something like this: > > > Thread report > > > Thread 0 - System ID 6420Entry point php_cgi!mainCRTStartup > Create time 28/12/13 19:02:36 > Time spent in user mode 0 Days 00:00:01.154 > Time spent in kernel mode 0 Days 00:00:00.078 > > > Function > php5_debug!zend_mm_check_ptr+1a7 php5_debug!_zend_mm_free_int+76 > php5_debug!_efree+77 php5_debug!_zval_dtor_func+ed > php_opcache!_zval_dtor+4d php_opcache!optimizer_compact_literals+743 > php_opcache!zend_optimize+5542 php_opcache!zend_accel_optimize+188 > php_opcache!zend_accel_script_optimize+90 > php_opcache!cache_script_in_shared_memory+4f > php_opcache!compile_and_cache_file+7cd > php_opcache!persistent_compile_file+753 > php5_debug!ZEND_INCLUDE_OR_EVAL_SPEC_TMP_HANDLER+318 > php5_debug!execute_ex+71 php5_debug!zend_execute+3f > php5_debug!zend_execute_scripts+1f0 php5_debug!php_execute_script+464 > php_cgi!main+1b9a php_cgi!__tmainCRTStartup+19d php_cgi!mainCRTStartup+e > kernel32!BaseThreadInitThunk+d ntdll!RtlUserThreadStart+1d > yeah, that's the victory :) Could you please file a bug using this BT? Maybe ping Dmitry as well. Btw. as Pierre said, WinDbg could be used for that as well. That's even much more powerful tool, it also has a console interface which works similar to gdb. Here's the site with quick links about it http://windbg.org/ Regards anatol