Bill, Rbb...
we never decided the canonical order of operations between core and http. See
os/win32/modules.c for our 'current' ordering.
I don't know precisely your issues (I'm buried in other things as you are both
aware) but keep in mind all of the http/core protocol stuff will become rather messy
unless we decide what we load when, mpm's, core and http. If we ultimately have an
http-less server (ugh!) consider the core and mpm need to load first, which is which
I don't really know.
Bill
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 20, 2001 5:21 PM
Subject: Re: cvs commit: httpd-2.0/server protocol.c
> On Fri, 20 Apr 2001, Bill Stoddard wrote:
>
> > I am fairly sure this patch is at least a contributing factor to a seg fault I am
>trying to debug.
> > The seg fault, which happens on the first request to the server, is in
>ap_getline(). req_cfg is
> > NULL after the call to ap_get_module_config(). We blow up trying to reference
>req_cgg->bb. with a
> > NULL pointer. Here is the code snip...
> >
> > req_cfg = (core_request_config *)
> > ap_get_module_config(r->request_config, &core_module);
> > b = req_cfg->bb
> >
> > The problem is that ap_set_module_config() has not been called on core_module yet.
> Ryan, did this
> > code serve pages for you before you committed it?
>
> This code has served static pages and SSI pages for me.
>
> I will try to look at what you are seeing later today.
>
> Ryan
>
> _______________________________________________________________________________
> Ryan Bloom [EMAIL PROTECTED]
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
>
>
