"lucky" me... when viewing the callstack, I get:
msvcr70d.dll!strlen() Line 78 Asm
php5ts_debug.dll!_estrdup(const char * s=0x058acf70, char * __zend_filename=0x0171d6f8, unsigned int __zend_lineno=510, char * __zend_orig_filename=0x00000000, unsigned int __zend_orig_lineno=0) Line 400 + 0x9
php5ts_debug.dll!zm_activate_spl(int type=1, int module_number=16, void * * * tsrm_ls=0x0193beb0) Line 510 + 0x28
php5ts_debug.dll!module_registry_request_startup(_zend_module_entry * module=0x00b89b28, void * * * tsrm_ls=0x0193beb0) Line 1543 + 0x1b
php5ts_debug.dll!zend_hash_apply(_hashtable * ht=0x018137c0, int (void *, void * * *)* apply_func=0x01001782, void * * * tsrm_ls=0x0193beb0) Line 664 + 0x10
php5ts_debug.dll!zend_activate_modules(void * * * tsrm_ls=0x0193beb0) Line 793 + 0x13
php5ts_debug.dll!php_request_startup(void * * * tsrm_ls=0x0193beb0) Line 1053 + 0x9
php5apache2.dll!php_apache_request_ctor(request_rec * r=0x005e0b70, php_struct * ctx=0x005e2948, void * * * tsrm_ls=0x0193beb0) Line 445 + 0xc
php5apache2.dll!php_handler(request_rec * r=0x005e0b70) Line 534 + 0x11
libhttpd.dll!ap_run_handler(request_rec * r=0x005e0b70) Line 153 + 0x25
libhttpd.dll!ap_invoke_handler(request_rec * r=0x005e0b70) Line 368
libhttpd.dll!ap_process_request(request_rec * r=0x005e0b70) Line 253
libhttpd.dll!ap_process_http_connection(conn_rec * c=0x005daa18) Line 251 + 0x6
libhttpd.dll!ap_run_process_connection(conn_rec * c=0x005daa18) Line 43 + 0x25
libhttpd.dll!ap_process_connection(conn_rec * c=0x005daa18, void * csd=0x005da948) Line 176 + 0x6
libhttpd.dll!worker_main(long thread_num=2080391471) Line 730
msvcr70.dll!free(void * pBlock=0x058acf70) Line 103 + 0x5
which simply tells me PHP started up fine, transfered control to Apache, and then died :|
So... that would point to a bug in apache, right?
- tul
Edin Kadribasic wrote:
Do you get a windows dialog with "this application did something really bad..."?
If you do pressing "Cancel" should start the debugger automatically. You'd need to compile php in the debug mode in order to get some useful information out of it though.
Edin
----- Original Message ----- From: "M. Sokolewicz" <tularis@xxxxxxx>
To: <php-windows@xxxxxxxxxxxxx>
Sent: Tuesday, March 22, 2005 5:17 PM
Subject: howto do a backtrace on windows?
hello,
I've compiled PHP (and apache) on windows (using MSVC++.NET), and have been doing so for a while now. Lately I've noticed Apache crashing when I run certain scripts, so I figured I'd best make a backtrace in such cases (since the scripts it crashes on are pretty long and complex, so getting to the code that makes it crash is pretty hard). However, I'm unsure how I can backtrace what hapenned before it crashed. I've tried using the gdb (GNU Debugger), but it returns only "??" for each item in the stack, even though PHP itself is built with debug symbols. Maybe apache should aswell?? I'm not sure how to continue here... =/
Does anyone have any tips/advice? (except for the "get a precompiled snapshot from php.net one)
thanks, - tul
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
