Fails to load xdebug - why?

[Dude_S]

I'm trying to install the debugger extension Xdebug [xdebug.org] for PHP on Apache running on my local Mac. I tried the built-in PHP installation and also the Entropy PHP package [entropy.ch]. I got the extension from the Xebug site and also a precompiled version from Komodo [code.activestate.com]. It's a PPC Mac and the extension is said to be universal binary, i.e. works on PPC Macs.

Xdebug never shows up in the phpinfo(); output, even though it loads the correct php.ini file (double-checked in output) and the .ini file specifies the extension correctly.

No matter what PHP/Xdebug combo, when I restart Apache, I see something like this in my error log:

[Fri Mar 04 12:26:49 2011] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
Failed loading /usr/local/php5/lib/php/extensions/no-debug-non-zts-20060613/xdebug.so: (null)
[Fri Mar 04 12:26:50 2011] [notice] Digest: generating secret for digest authentication ...
[Fri Mar 04 12:26:50 2011] [notice] Digest: done
[Fri Mar 04 12:26:50 2011] [notice] Apache/2.2.14 (Unix) mod_ssl/2.2.14 OpenSSL/0.9.7l DAV/2 PHP/5.2.9 configured -- resuming normal operations

Is there any way to get more info about why it failed loading? The error message just says (null) - not very helpful. Any other ideas?

[Dude_S]

Any ideas?

I think this may be an Apache issue because I tried two different PHP builds and two different Xdebug builds, all fail the same way and the only constant is the Mac OS built-in Apache.

[jdMorgan]

With this level of specificity, you might want to ask in our PHP forum, or in an Xdebug-specific forum.

We're strongest here on questions about the Apache server itself, and it's quite possible that no one reading here has ever tried Xdebug (i.e. you're the first).

Jim

[Dude_S]

Ok, I understand.

Is there a way to elicit more verbose error messages though? It would help if Apache told me why it failed loading instead of just "null".

[jdMorgan]

It looks like you've already got your ErrorLevel set very low. So if Apache isn't logging any more-specific errors, it's likely because it isn't being passed any additional info to log...

Jim