Alan Knowles wrote:
> > What does this line in your midgard.c say? In the CVS version line 340 this
> > is not in rinit.
>
> try php4/midgard.c 430 - line 430 is the
Ah yes.
> also be able to get this
> */
> php_error(E_NOTICE, "Cannot get midgard module directory config");
> MGDG(rcfg) = NULL;
> MGDG(dcfg) = NULL;
> return SUCCESS;
> }
> #endif <-- thisone is 430
That's not exactly a likely spot for a segfault. This is the error
line reported from the sources you compiled?
> MGDG(mgd) = MGDG(rcfg)->mgd;
> ALLOC_INIT_ZVAL(MGDG(udf));
> if(MGDG(udf)) array_init(MGDG(udf));
>
> the only thoughts here? = MGDG
MGDG = MiDGard Global. It's a PHP thing.
> At this point, the virtual host would not have had mod midgard run correctly
> as MidgardEngine was not set.
mod_midgard is running nonetheless, it's just declining requests.
> so would any of the MGDG(rcfg) etc calls be causing problems...
They shouldn't, they should just be NULL.
> or what is MIDGARD_PHP_REQUEST_CONFIG_BUG_WORKAROUND ??
There is a bug in PHP that causes request_config to be 0x10000 when
accessed from a PHP extension. This workaround stores the relevant
addresses in midgard-lib temporarily. It's enabled by default in
recent CVS, but you need to download all three parts for it to work.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
