Emiliano <[EMAIL PROTECTED]> wrote:
> David Guerizec wrote:
>
> > Again, testing r against NULL won't do what you want, I've experienced that r
> > stayed normal, while r->request_config simply changed from a normal pointer
> > address (like 0x8b5f1234) to 0x1000 (dec 65536, seems to be a error code, or a
> > flag) between mod_midgard and PHP_MINIT... but as I said before, once apache
> > was compiled with debug symbols, all worked fine.
>
> OK, I think I have the same problem now. Bugger me where this comes
> from, but at least I can look for it now. No problems with starting
> apache though, so I can't yet reproduce the problem where libmidgard
> isn't found. This is on debian unstable, updated last night.
did you load midgard.so from php.ini ? if so, you shouldn't be able to start apache,
otherwise it will segfault in midgard-root.php.
> Emile
--
Best regards, David Guerizec
http://www.guerizec.net/david/ http://www.imuable.org/
http://www.midgard-project.org/ http://www.aurora-linux.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
