Emiliano <[EMAIL PROTECTED]> said:
> Alan Knowles wrote:
>
> > We are getting apache segafault when serving no midgard sites
> >
> > backtrace below - (temporay solution is to take midgard.so out of php.ini
and
> > just let midgard-root.php handle it.)
> >
> > regards
> >
> > alan
> >
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x407e3ffb in php_rinit_midgard (type=1, module_number=17) at
midgard.c:430
> > 430 midgard.c: No such file or directory.
> > in midgard.c
>
> 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
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
MGDG(mgd) = MGDG(rcfg)->mgd;
ALLOC_INIT_ZVAL(MGDG(udf));
if(MGDG(udf)) array_init(MGDG(udf));
the only thoughts here? = MGDG
At this point, the virtual host would not have had mod midgard run correctly
as MidgardEngine was not set.
so would any of the MGDG(rcfg) etc calls be causing problems...
or what is MIDGARD_PHP_REQUEST_CONFIG_BUG_WORKAROUND ??
> Emile
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
Technical Director
Linux Center (HK) Ltd.
www.hklc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
