"Anatol Belski" in php.windows (Thu, 26 Dec 2013 23:10:41 +0100): >Yeah, there is a page >https://bugs.php.net/bugs-generating-backtrace-win32.php , the debug tool >is in current version 2.0 now, but the screenshots are compatible. I am now getting this result with a x64 debug build: WARNING - DebugDiag was not able to locate debug symbols for \php5_debug.dll, so the information below may be incomplete. In php-cgi__PID__2664__Date__12_28_2013__Time_02_21_08PM__334__Second_Chance_Exception_C0000005.dmp the assembly instruction at php5_debug!gc_init+2687d in D:\phpdev\php57nts.x64d\php5_debug.dll from The PHP Group has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 0 Strange thing: there was a php5_debug.pdb besides the php5_debug.dll. Am I missing something? The info does not go further than things like: php5_debug!gc_init+2687d php5_debug!gc_init+2684a php5_debug!gc_init+23c67 php5_debug!gc_init+21488 php5_debug!gc_init+1c658e php5_debug!gc_init+14868d php5_debug!gc_init+14a008 There are a lot more files with info about php5_debug.dll than only the .pdb: 28/12/13 14:56 16.347.648 php5_debug.dll 28/12/13 14:48 32.697 php5_debug.dll.def 28/12/13 14:56 618 php5_debug.dll.manifest 28/12/13 14:51 1.132 php5_debug.dll.res 28/12/13 14:56 488.426 php5_debug.exp 28/12/13 14:56 7.497.392 php5_debug.ilk 28/12/13 14:56 806.446 php5_debug.lib 28/12/13 14:56 15.346.688 php5_debug.pdb Which one would be interesting for the debugdiag tool? >The issue with gdb is that it can debug only the corresponding builds (for >instance binaries compiled with gcc under mingw). Hmmm. GDB knew that it was zend_mm_set_custom_handlers in the DLL. Jan -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
