I've had this one bite me in the ass as well. Same thing if you accidentally get duplicate LoadModule lines in there on a shared module, IIRC. Would there ever be a *legitimate* reason to load the same module more than once?
--Cliff ---------- Forwarded message ---------- Date: Tue, 16 Apr 2002 14:52:07 +0100 From: Nigel Cole To: [EMAIL PROTECTED] Subject: Bugzilla bug 8034 - possible explanation of core dump I've also been getting a core dump from Apache 2.0.35 under Solaris, but it turned out to be more of a missing feature than a bug: I'd compiled mod_ssl statically, but accidentally left in the LoadModule command for the previously-compiled dynamic version. Apache 2 loaded the dynamic module without complaint, but later mySrvConfig returned NULL when trying to get the server configuration structure, followed by a segmentation fault when trying to write to the NULL structure (line 593 of ssl_engine_config.c). After I removed the LoadModule line, the problem went away. I think, from the description of the second problem in the Bugzilla report, the user may have made the same mistake. Apache probably ought to detect that a module it's dynamically loading has already been loaded statically, and at least generate a warning.
