How to get stack trace when WAMP server crashes?

Several times my WAMP server crashes. I get the following error.

HTTP has encountered exception and needs to close.
Unreferenced Memory.
szAppName : httpd.exe     szAppVer : 2.2.11.0     szModName : php5ts.dll     
szModVer : 5.3.0.0     offset : 0000c309     


C:\DOCUME~1\blrcom\LOCALS~1\Temp\WERc677.dir00\httpd.exe.mdmp
C:\DOCUME~1\blrcom\LOCALS~1\Temp\WERc677.dir00\appcompat.txt

My question is: how to get a stack trace to debug this problem? Should I use a window debugger, a window debugger, or is there any settings in the WAMP server configuration, should I enable it?

+3
source share
2 answers

You can use Debug Diag .
Select the Failure rule in the Select Rule Type dialog box that appears when Debug Diag starts.

Tess Ferrandez ​​ Debug Diag 1.1. ( , , , ; -))


, "" . Microsoft " ", , .pdb.
" php5ts! Zend_mm_shutdown + f69". zend_mm_shutdown, php5ts.dll, "" , . , zend_mm_shutdown + f69. ​​, .
, ( , , ). php.
php.net/win32 http://windows.php.net/download/. . wamp php.net(.. /dll ).

, , , . - . Mm zend_mm_shutdown, , " ". , , . , zend. , (, , /). - ... , , , , . zend_mm_shutdown , , , ( ).
php- , . wamp php.net. , php wamp, , apache.
/ ... ; -)

+1

php 5.3.0. PDO, MySql?? . , .

61 - ID 2760 msvcrt! _endthreadex + 3a 3/31/2010 5:25:46 , 0 0: 0: 16,593 , 0 0: 0: 0.453

Arg 1 Arg 2 Arg 3 php5ts! _zend_mm_free_int + 139 0288a878 00020004 008eff46
php5ts! _efree + 36 0110ff48 02d18868 0090e442
php5ts! _zval_ptr_dtor + 66 024ffa88 02d18770 02d18848
php5ts! zend_std_write_property + 1f2 02d18848 0110ff48 02d18868
php5ts! pdo_stmt_construct + 7d 02d1b968 02d18848 0110eb90
php5ts! zim_PDO_prepare + 428 0110eb90 02d18848 00000000
php5ts! zend_do_fcall_common_helper_SPEC + 946 024ffbf8 028894c8 024ffe74
php5ts! execute + 29e 02d40070 02889400 00000000
php5ts! zend_execute_scripts + f6 00000008 028894c8 00000000
php5ts! php_execute_script + 22d 024ffe74 028894c8 00000005
php5apache2_2! php_handler + 5d0 03249f98 008238b8 03249f98
libhttpd! ap_run_handler + 21 03249f98 03249f98 03249f98
libhttpd! ap_invoke_handler + ae 00000000 029e9fd8 024fff38
libhttpd! ap_die + 29e 03249f98 00000000 00788168
libhttpd! ap_get_request_note + 1c9c 029e9fd8 029e9fd8 029e9fd8
libhttpd! ap_run_process_connection + 21 029e9fd8 00775050 024fff80
libhttpd! ap_process_connection + 33 029e9fd8 027de3f0 00ed0000
libhttpd! ap_regkey_value_remove + c7c 029e9fd0 00ed0000 00f10000
msvcrt! _endthreadex + a9 011d3088 00ed0000 00f10000
kernel32! BaseThreadStart + 37 77c3a341 011d3088 00000000

0

Source: https://habr.com/ru/post/1736852/


All Articles