Stas,
I am sorry, I got too excited when I saw the segmentation fault.
Here is the output of 'bt':
Program received signal SIGSEGV, Segmentation fault.
0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
778 if (!(r->finfo.st_mode & S_IXUSR)) {
(gdb) bt
#0 0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
#1 0x17aeb0 in ap_invoke_handler ()
#2 0x199a28 in process_request_internal ()
#3 0x199aac in ap_process_request ()
#4 0x18c948 in child_main ()
#5 0x18cbdc in make_child ()
#6 0x18cdf8 in startup_children ()
#7 0x18d82c in standalone_main ()
#8 0x18e488 in main ()
Thanks for offering to help!
Alex
>From: Stas Bekman <[EMAIL PROTECTED]>
>To: Alex Lee <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: Segmentation Fault with mod_php and mod_perl
>Date: Wed, 28 Aug 2002 11:00:42 +0800
>
>Alex Lee wrote:
>
>> This is what I got from core backtrace:
>>
>>gdb /usr/local/src/apache/current/src/httpd
>[...]
>>Program received signal SIGSEGV, Segmentation fault.
>>0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
>>778 if (!(r->finfo.st_mode & S_IXUSR)) {
>
>please finish reading the section explaining how to get the backtrace.
>You've got only the first frame. You need to execute 'bt' or 'where' to get
>it all.
>
>>Are you going to say this is a PHP bug? :-)
>>But how come if I only activate PHP module, it works fine.
>
>Something affects a datastructure which PHP uses and segfaults in it. But
>get first the whole backtrace.
>
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
