On every apache ebuild since 2.0.49-r1, apache segfaults upon first access. If not run in debug mode (-X), the apache process itself does not die, but the thread does, producing a message such as this in /var/log/apache2/error_log: [Fri Jul 09 23:03:22 2004] [notice] child pid 5161 exit signal Segmentation fault (11) If run in debug mode, the apache process will die, leaving a zombie-like process in the background that must be killed. The page I'm attempting to access is a straight index.html page. The apache-2.0.49 ebuild (which is no longer in portage, but available in the CVS attic) works fine. Reproducible: Always Steps to Reproduce: 1. emerge apache-2.0.50 2. run /sbin/apache2 -X 3. run lynx http://localhost Actual Results: Lynx fails to open the page because the thread servicing it has segfaulted. Expected Results: I would expect the page to be served. root@tsubame(47)# emerge info Portage 2.0.50-r8 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.4.25) ================================================================= System uname: 2.4.25 i686 Intel(R) Xeon(TM) CPU 2.40GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O2 -pipe" DISTDIR="/usr/local/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apache2 apm arts audiofile avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm gif gimpprint gnome gpm gtk gtk2 gtkhtml guile imap imlib jack java joystick jpeg kde libg++ libwww mad mikmod motif mozilla moznocompose moznoirc moznomail mozsvg mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres ppds python qt quicktime readline ruby ruby18 scanner sdl slang spell ssl svga tcltk tcpd tetex tiff truetype x86 xml2 xmms xv zlib" Please find attached the output of strace and gdb.
Created attachment 35095 [details] The output of strace /usr/sbin/apache2 -X
Created attachment 35096 [details] the output of gdb /usr/sbin/apache2
Please submit bug with issues.apache.org
I would like to report this upstream, but the upstream package (distfiles/httpd-2.0.50.tar.gz) works fine, even after I enabled the modules as specified by my unmodified /etc/apache2/apache2-builtin-mods. From this, I can only conclude that it has something to do with how the ebuild is patching or configuring the package. If I am still to report this upstream, perhaps you can give me a little help with my upstream bug report as to how gentoo is doing things differently. I will attach a script indicating how I configured the upstream package.
Created attachment 35180 [details] My working configure for the upstream tarball
Seems to be fixed in 2.0.51-r1.
This finally works again for me in 2.0.52.
Closing.
