Thommie Rother wrote:
> today I had some long IRC sessions sorting out my midgard probs. Aside
> from the probs I had in connecting to mysql.sock (apparently this was
> due to some wrong directory permissions which only showed up when using
> socks), we investigated that the segmentastion fault problem is even
> present on SUSE and even on apache 1.3.14. Thats what we did:
>
> 1) http://localhost:80/asgard/ The PW Dialog shows up, but login
> fails. In the log I see
mod_midgard handles the auth, and this works.
> 2) we uncommented php.ini "extension=midgard.so" and
> changed midgard-root.php so that it contains
>
> phpinfo ();
>
> This worked OK - browser sent the php info stuff. No probs with the
> khandler or db connect any more.
>
> 3) We added to midgard-root.php
>
> dl ("midgard.so");
I know this is in the midgartd-root.php right now, but I'm not sure
this is going to work. The Midgard extension does required setup in
MINIT and RINIT -- are these executed for dlopened libs? My first
hunch would be not.
> Midgard: select_database kept current (midgard)
> [Fri Apr 27 19:21:37 2001] [notice] child pid 8629 exit signal
> Segmentation fault (11)
>
> The seg fault was reproducible on suse 7.1, either with apache 1.3.19
> or with (downgraded) 1.3.14. The midgard was compiled with 1.3.14
> installed.
>
> Please don't asked if I tested my libs or anything else, I feel like we
> already tested everything ;-(
I've compiled a mini PHP extension that exhibits the exact same
problem (request_config being bogus) without any trace of midgard
being active. I hope we'll get this resolved on the php-dev list
soon.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
