Justin Erenkrantz wrote:
>
> On Tue, Oct 23, 2001 at 05:00:04PM -0400, Greg Ames wrote:
> > Feeling brave, I decided to build with the threaded MPM and try a log
> > replay. I got a bunch of seg faults very quickly, no dump, and got
> > seg-fault-but-no-dump log messages. ps makes it look like the main
> > thread bailed out before all its worker threads exited. The server then
> > became useless.
> >
> > I re-built with the worker MPM, and got very similar results.
>
> FWIW, I took a fresh CVS checkout and worker is restarting fine for
> me. Can anyone else reproduce this? I tried killing off processes
> (sending the child a SIGKILL directly), and worker spawned off a new
> process accordingly (yay!) - took about a second, but that's the
> idle server maint period, IIRC.
I should have mentioned earlier - this is on Linux 2.2.19. I'll try
Linux 2.4.6 and Solaris.
A SIGKILL from one process to another may not be the same thing as a
SIGSEGV that a single thread sends to itself. Can you recover from a
seg fault on a thread? and what platform?
This generates seg faults whenever you try to access mod_info:
Index: modules/generators/mod_info.c
===================================================================
RCS file: /cvs/apache/httpd-2.0/modules/generators/mod_info.c,v
retrieving revision 1.40
diff -u -d -b -r1.40 mod_info.c
--- mod_info.c 2001/08/11 04:04:12 1.40
+++ mod_info.c 2001/10/24 14:46:20
@@ -377,6 +377,8 @@
if (r->method_number != M_GET)
return DECLINED;
+ r = (request_rec *) NULL; /* to test seg faults DO NOT COMMIT!
gla */
+
r->content_type = "text/html";
if (r->header_only) {
return 0;
Greg
