Hi there, On Sat, 17 Nov 2001, Dau Hee wrote:
[snip,snip] > I also use up2date to upgraded my glibc to 2.2.4 from 2.2.2. Why? If it ain't broke, don't mend it. > After the glibc upgrade, I cannot get Apache to run. Not too surprising after upgrading glibc. Have you recompiled Perl itself? Are you sure that you are using all the newly compiled code (did you "make install")? > The odd thing about this is that when Apache dies, > nothing is printed on my console. Nothing is printed > to error_log as well [snip] This is not unusual when you get a segfault. [snip] > Program received signal SIGSEGV, Segmentation fault. [snip] > (gdb) bt > #0 0x403a388f in S_new_xpvmg () from > /etc/httpd/modules/libperl.so [snip] > Unfortunately I do not know what it means. It means that mod_perl is crashing, a segmentation fault (segfault) is when the process running your code tries to reach an area of memory to which it is not allowed access. Typically the code tries to call a C function like free() for an area of memory which has already been free()d, or maybe it runs off the end of an array (not a Perl array!) or simply does an indexed write using an uninitialised pointer. The processor sends a signal (memory protection fault) to the operating system, which kills the offending process. You could try rebuilding mod_perl statically, see http://perl.apache.org/guide but if I'd rebuilt absolutely everything and I were sure that glibc caused the problem I'd be tempted to go back to the earlier glibc. > I would really like to use install_driver since I read in the > mod_perl line that this will reduce the memory usage in each child. If your machine is OK without it, don't worry about it too much. 73, Ged.
