Re: SOLVED Problem with mod_php4 and Apache 1.3.29 in CURRENT

Manfred Antar wrote:

>At 08:10 PM 12/17/2003, Scott W wrote:
>  
>
>>Scott W wrote:
>>
>>    
>>
>>>Hey all...any advice appreciated, but it appears that mod_php4 as well as the full lang/php4 in combination with apache manages to core apache every time I've tried it.  Recent cvsup from past week, along with current as of a few hours ago today, rebuild of entire system, apache, php4 and mod_php4 all have the same results- apache cores on startup with the following stack trace:
>>>
>>>Script started on Wed Dec 17 20:50:48 2003
>>>You have mail.
>>>freeb# gdb /usr/local/sbin/apachectl httpd httpd.core
>>>GNU gdb 5.2.1 (FreeBSD)
>>>This GDB was configured as "i386-undermydesk-freebsd"...
>>>(no debugging symbols found)...
>>>Core was generated by `httpd'.
>>>Program terminated with signal 11, Segmentation fault.
>>>Reading symbols from /lib/libcrypt.so.2...(no debugging symbols found)...done.
>>>Loaded symbols for /lib/libcrypt.so.2
>>>Reading symbols from /usr/local/lib/libexpat.so.4...
>>>(no debugging symbols found)...done.
>>>Loaded symbols for /usr/local/lib/libexpat.so.4
>>>Reading symbols from /lib/libc.so.5...(no debugging symbols found)...done.
>>>Loaded symbols for /lib/libc.so.5
>>>Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...
>>>done.
>>>Loaded symbols for /libexec/ld-elf.so.1
>>>#0  0x28d8f8a0 in ?? ()
>>>(gdb) bt
>>>#0  0x28d8f8a0 in ?? ()
>>>#1  0x281716ec in nsdispatch () from /lib/libc.so.5
>>>#2  0x2814b0b5 in getpwnam_r () from /lib/libc.so.5
>>>#3  0x2814b30b in getpwuid_r () from /lib/libc.so.5
>>>#4  0x2814b25b in getpwuid_r () from /lib/libc.so.5
>>>#5  0x2814b3d9 in getpwnam () from /lib/libc.so.5
>>>#6  0x08069638 in ap_uname2id ()
>>>#7  0x08054786 in init_config_globals ()
>>>#8  0x080549d1 in ap_read_config ()
>>>#9  0x0805e43a in standalone_main ()
>>>#10 0x0805ed1a in main ()
>>>#11 0x0804e4f2 in _start ()
>>>(gdb) q
>>>uname -a
>>>FreeBSD freeb.swtechnical.com 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Dec 16 19:18:17 EST 2003     
>>>root_at_freeb.swtechnical.com:/usr/src/sys/i386/compile/SMP52  i386
>>>Script done on Wed Dec 17 20:51:15 2003
>>>
>>>Removing the
>>>LoadModule php4_module  libexec/apache/libphp4.so
>>>and
>>>AddModule mod_php4.c
>>>
>>>lines from the httpd.conf file allows apache to run properly....not that that helps much when you need to enable php ;-)
>>>
>>>Scott
>>>      
>>>
>>Following up to myself ;-)  It appears to have been one of the options selected for PHP install, although I'm unsure as to which yet...have stripped options/left at default for testing, and the default options do work w/apache....may need to do a few more builds to see if I can determine which option (or combination thereof) cause the issue w/use as an apache module...
>>
>>Scott
>>
>>
>>_______________________________________________
>>freebsd-current_at_freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>>    
>>
>
>I had problems when I compiled in mnogosearch with php4
>Dumped core every time I tried to start apache.
>without it, no problem
>This is on a machine running 5.2 current i386
>Manfred
>
>==================================
>||      null_at_pozo.com           ||
>||      Ph. (415) 681-6235      ||
>================================== 
>
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
>  
>
Manfred- thanks, that appears at this point to have been the problem.  
Also disabled IMAP support per someone else's comments, will see 
hopefully this weekend if it works for 'real use' now...

Thanks,

Scott